<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/block/swim.c, branch v4.19.112</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v4.19.112</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v4.19.112'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2018-11-13T19:08:20+00:00</updated>
<entry>
<title>swim: fix cleanup on setup error</title>
<updated>2018-11-13T19:08:20+00:00</updated>
<author>
<name>Omar Sandoval</name>
<email>osandov@fb.com</email>
</author>
<published>2018-10-11T19:20:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=2ee36fb7c3a635d9db4e7692a14e31535c273a22'/>
<id>urn:sha1:2ee36fb7c3a635d9db4e7692a14e31535c273a22</id>
<content type='text'>
[ Upstream commit 1448a2a5360ae06f25e2edc61ae070dff5c0beb4 ]

If we fail to allocate the request queue for a disk, we still need to
free that disk, not just the previous ones. Additionally, we need to
cleanup the previous request queues.

Signed-off-by: Omar Sandoval &lt;osandov@fb.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
Signed-off-by: Sasha Levin &lt;sashal@kernel.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>block/swim: Select appropriate drive on device open</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b3906535ccc6cd04c42f9b1c7e31d1947b3ebc74'/>
<id>urn:sha1:b3906535ccc6cd04c42f9b1c7e31d1947b3ebc74</id>
<content type='text'>
The driver supports internal and external FDD units so the floppy_open
function must not hard-code the drive location.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Fix IO error at end of medium</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=5a13388d7aa1177b98d7168330ecbeeac52f844d'/>
<id>urn:sha1:5a13388d7aa1177b98d7168330ecbeeac52f844d</id>
<content type='text'>
Reading to the end of a 720K disk results in an IO error instead of EOF
because the block layer thinks the disk has 2880 sectors. (Partly this
is a result of inverted logic of the ONEMEG_MEDIA bit that's now fixed.)

Initialize the density and head count in swim_add_floppy() to agree
with the device size passed to set_capacity() during drive probe.

Call set_capacity() again upon device open, after refreshing the density
and head count values.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Check drive type</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8a500df63d07d8aee44b7ee2c54e462e47ce93ec'/>
<id>urn:sha1:8a500df63d07d8aee44b7ee2c54e462e47ce93ec</id>
<content type='text'>
The SWIM chip is compatible with GCR-mode Sony 400K/800K drives but
this driver only supports MFM mode. Therefore only Sony FDHD drives
are supported. Skip incompatible drives.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Rename macros to avoid inconsistent inverted logic</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=56a1c5ee54f69dd767fb61d301883dc919ddc259'/>
<id>urn:sha1:56a1c5ee54f69dd767fb61d301883dc919ddc259</id>
<content type='text'>
The Sony drive status bits use active-low logic. The swim_readbit()
function converts that to 'C' logic for readability. Hence, the
sense of the names of the status bit macros should not be inverted.

Mostly they are correct. However, the TWOMEG_DRIVE, MFM_MODE and
TWOMEG_MEDIA macros have inverted sense (like MkLinux). Fix this
inconsistency and make the following patches less confusing.

The same problem affects swim3.c so fix that too.

No functional change.

The FDHD drive status bits are documented in sonydriv.cpp from MAME
and in swimiii.h from MkLinux.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Cc: linuxppc-dev@lists.ozlabs.org
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Don't log an error message for an invalid ioctl</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8e2ab5a4efaac77fb93e5b5b109d0b3976fdd3a0'/>
<id>urn:sha1:8e2ab5a4efaac77fb93e5b5b109d0b3976fdd3a0</id>
<content type='text'>
The 'eject' shell command may send various different ioctl commands.
This leads to error messages on the console even though the FDEJECT
ioctl succeeds.

~# eject floppy
SWIM floppy_ioctl: unknown cmd 21257
SWIM floppy_ioctl: unknown cmd 1

Don't log an error message for an invalid ioctl, just do as the
swim3 driver does and return -ENOTTY.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Remove extra put_disk() call from error path</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c1d6207cc0eef2a7f8551f9c7420d8776268f6e1'/>
<id>urn:sha1:c1d6207cc0eef2a7f8551f9c7420d8776268f6e1</id>
<content type='text'>
Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Fixes: 103db8b2dfa5 ("[PATCH] swim: stop sharing request queue across multiple gendisks")
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>block/swim: Fix array bounds check</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=7ae6a2b6cc058005ee3d0d2b9ce27688e51afa4b'/>
<id>urn:sha1:7ae6a2b6cc058005ee3d0d2b9ce27688e51afa4b</id>
<content type='text'>
In the floppy_find() function in swim.c is a call to
get_disk(swd-&gt;unit[drive].disk). The actual parameter to this call
can be a NULL pointer when drive == swd-&gt;floppy_count. This causes
an oops in get_disk().

Data read fault at 0x00000198 in Super Data (pc=0x1be5b6)
BAD KERNEL BUSERR
Oops: 00000000
Modules linked in: swim_mod ipv6 mac8390
PC: [&lt;001be5b6&gt;] get_disk+0xc/0x76
SR: 2004  SP: 9a078bc1  a2: 0213ed90
d0: 00000000    d1: 00000000    d2: 00000000    d3: 000000ff
d4: 00000002    d5: 02983590    a0: 02332e00    a1: 022dfd64
Process dd (pid: 285, task=020ab25b)
Frame format=B ssw=074d isc=4a88 isb=6732 daddr=00000198 dobuf=00000000
baddr=001be5bc dibuf=bfffffff ver=f
Stack from 022dfca4:
        00000000 0203fc00 0213ed90 022dfcc0 02982936 00000000 00200000 022dfd08
        0020f85a 00200000 022dfd64 02332e00 004040fc 00000014 001be77e 022dfd64
        00334e4a 001be3f8 0800001d 022dfd64 01c04b60 01c04b70 022aba80 029828f8
        02332e00 022dfd2c 001be7ac 0203fc00 00200000 022dfd64 02103a00 01c04b60
        01c04b60 0200e400 022dfd68 000e191a 00200000 022dfd64 02103a00 0800001d
        00000000 00000003 000b89de 00500000 02103a00 01c04b60 02103a08 01c04c2e
Call Trace: [&lt;02982936&gt;] floppy_find+0x3e/0x4a [swim_mod]
 [&lt;00200000&gt;] uart_remove_one_port+0x1a2/0x260
 [&lt;0020f85a&gt;] kobj_lookup+0xde/0x132
 [&lt;00200000&gt;] uart_remove_one_port+0x1a2/0x260
 [&lt;001be77e&gt;] get_gendisk+0x0/0x130
 [&lt;00334e4a&gt;] mutex_lock+0x0/0x2e
 [&lt;001be3f8&gt;] disk_block_events+0x0/0x6c
 [&lt;029828f8&gt;] floppy_find+0x0/0x4a [swim_mod]
 [&lt;001be7ac&gt;] get_gendisk+0x2e/0x130
 [&lt;00200000&gt;] uart_remove_one_port+0x1a2/0x260
 [&lt;000e191a&gt;] __blkdev_get+0x32/0x45a
 [&lt;00200000&gt;] uart_remove_one_port+0x1a2/0x260
 [&lt;000b89de&gt;] complete_walk+0x0/0x8a
 [&lt;000e1e22&gt;] blkdev_get+0xe0/0x29a
 [&lt;000e1fdc&gt;] blkdev_open+0x0/0xb0
 [&lt;000b89de&gt;] complete_walk+0x0/0x8a
 [&lt;000e1fdc&gt;] blkdev_open+0x0/0xb0
 [&lt;000e01cc&gt;] bd_acquire+0x74/0x8a
 [&lt;000e205c&gt;] blkdev_open+0x80/0xb0
 [&lt;000e1fdc&gt;] blkdev_open+0x0/0xb0
 [&lt;000abf24&gt;] do_dentry_open+0x1a4/0x322
 [&lt;00020000&gt;] __do_proc_douintvec+0x22/0x27e
 [&lt;000b89de&gt;] complete_walk+0x0/0x8a
 [&lt;000baa62&gt;] link_path_walk+0x0/0x48e
 [&lt;000ba3f8&gt;] inode_permission+0x20/0x54
 [&lt;000ac0e4&gt;] vfs_open+0x42/0x78
 [&lt;000bc372&gt;] path_openat+0x2b2/0xeaa
 [&lt;000bc0c0&gt;] path_openat+0x0/0xeaa
 [&lt;0004463e&gt;] __irq_wake_thread+0x0/0x4e
 [&lt;0003a45a&gt;] task_tick_fair+0x18/0xc8
 [&lt;000bd00a&gt;] do_filp_open+0xa0/0xea
 [&lt;000abae0&gt;] do_sys_open+0x11a/0x1ee
 [&lt;00020000&gt;] __do_proc_douintvec+0x22/0x27e
 [&lt;000abbf4&gt;] SyS_open+0x1e/0x22
 [&lt;00020000&gt;] __do_proc_douintvec+0x22/0x27e
 [&lt;00002b40&gt;] syscall+0x8/0xc
 [&lt;00020000&gt;] __do_proc_douintvec+0x22/0x27e
 [&lt;0000c00b&gt;] dyadic+0x1/0x28
Code: 4e5e 4e75 4e56 fffc 2f0b 2f02 266e 0008 &lt;206b&gt; 0198 4a88 6732 2428 002c 661e 486b 0058 4eb9 0032 0b96 588f 4a88 672c 2008
Disabling lock debugging due to kernel taint

Fix the array index bounds check to avoid this.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: Jens Axboe &lt;axboe@kernel.dk&gt;
Cc: stable@vger.kernel.org # v4.14+
Fixes: 8852ecd97488 ("[PATCH] m68k: mac - Add SWIM floppy support")
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Reviewed-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>m68k/mac: Don't remap SWIM MMIO region</title>
<updated>2018-04-17T03:49:35+00:00</updated>
<author>
<name>Finn Thain</name>
<email>fthain@telegraphics.com.au</email>
</author>
<published>2018-04-12T00:50:14+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=b64576cbf36afa5fabf3b31f62a1994c429ef855'/>
<id>urn:sha1:b64576cbf36afa5fabf3b31f62a1994c429ef855</id>
<content type='text'>
For reasons I don't understand, calling ioremap() then iounmap() on
the SWIM MMIO region causes a hang on 68030 (but not on 68040).

~# modprobe swim_mod
SWIM floppy driver Version 0.2 (2008-10-30)
SWIM device not found !
watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [modprobe:285]
Modules linked in: swim_mod(+)
Format 00  Vector: 0064  PC: 000075aa  Status: 2000    Not tainted
ORIG_D0: ffffffff  D0: d00c0000  A2: 007c2370  A1: 003f810c
A0: 00040000  D5: d0096800  D4: d0097e00
D3: 00000001  D2: 00000003  D1: 00000000
Non-Maskable Interrupt
Modules linked in: swim_mod(+)
PC: [&lt;000075ba&gt;] __iounmap+0x24/0x10e
SR: 2000  SP: 007abc48  a2: 007c2370
d0: d00c0000    d1: 000001a0    d2: 00000019    d3: 00000001
d4: d0097e00    d5: d0096800    a0: 00040000    a1: 003f810c
Process modprobe (pid: 285, task=007c2370)
Frame format=0
Stack from 007abc7c:
        ffffffed 00000000 006a4060 004712e0 007abca0 000076ea d0080000 00080000
        010bb4b8 007abcd8 010ba542 d0096000 00000000 00000000 00000001 010bb59c
        00000000 007abf30 010bb4b8 0047760a 0047763c 00477612 00616540 007abcec
        0020a91a 00477600 0047760a 010bb4cc 007abd18 002092f2 0047760a 00333b06
        007abd5c 00000000 0047760a 010bb4cc 00404f90 004776b8 00000001 007abd38
        00209446 010bb4cc 0047760a 010bb4cc 0020938e 0031f8be 00616540 007abd64
Call Trace: [&lt;000076ea&gt;] iounmap+0x46/0x5a
 [&lt;00080000&gt;] shrink_page_list+0x7f6/0xe06
 [&lt;010ba542&gt;] swim_probe+0xe4/0x496 [swim_mod]
 [&lt;0020a91a&gt;] platform_drv_probe+0x20/0x5e
 [&lt;002092f2&gt;] driver_probe_device+0x21c/0x2b8
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;00209446&gt;] __driver_attach+0xb8/0xce
 [&lt;0020938e&gt;] __driver_attach+0x0/0xce
 [&lt;0031f8be&gt;] klist_next+0x0/0xa0
 [&lt;00207562&gt;] bus_for_each_dev+0x74/0xba
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;00208e44&gt;] driver_attach+0x1a/0x1e
 [&lt;0020938e&gt;] __driver_attach+0x0/0xce
 [&lt;00207e26&gt;] bus_add_driver+0x188/0x234
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;00209894&gt;] driver_register+0x58/0x104
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;010bd000&gt;] swim_init+0x0/0x2c [swim_mod]
 [&lt;0020a7be&gt;] __platform_driver_register+0x38/0x3c
 [&lt;010bd028&gt;] swim_init+0x28/0x2c [swim_mod]
 [&lt;000020dc&gt;] do_one_initcall+0x38/0x196
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;003331cc&gt;] mutex_unlock+0x0/0x3e
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;003331cc&gt;] mutex_unlock+0x0/0x3e
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;003331cc&gt;] mutex_unlock+0x0/0x3e
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;003331cc&gt;] mutex_unlock+0x0/0x3e
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;00075008&gt;] __free_pages+0x0/0x38
 [&lt;000045c0&gt;] mangle_kernel_stack+0x30/0xda
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;003331cc&gt;] mutex_unlock+0x0/0x3e
 [&lt;00333b06&gt;] mutex_lock+0x0/0x2e
 [&lt;0005ced4&gt;] do_init_module+0x42/0x266
 [&lt;010bd000&gt;] swim_init+0x0/0x2c [swim_mod]
 [&lt;000344c0&gt;] blocking_notifier_call_chain+0x0/0x20
 [&lt;0005eda0&gt;] load_module+0x1a30/0x1e70
 [&lt;0000465d&gt;] mangle_kernel_stack+0xcd/0xda
 [&lt;00331c64&gt;] __generic_copy_from_user+0x0/0x46
 [&lt;0033256e&gt;] _cond_resched+0x0/0x32
 [&lt;00331b9c&gt;] memset+0x0/0x98
 [&lt;0033256e&gt;] _cond_resched+0x0/0x32
 [&lt;0005f25c&gt;] SyS_init_module+0x7c/0x112
 [&lt;00002000&gt;] _start+0x0/0x8
 [&lt;00002000&gt;] _start+0x0/0x8
 [&lt;00331c82&gt;] __generic_copy_from_user+0x1e/0x46
 [&lt;0005f2b2&gt;] SyS_init_module+0xd2/0x112
 [&lt;0000465d&gt;] mangle_kernel_stack+0xcd/0xda
 [&lt;00002b40&gt;] syscall+0x8/0xc
 [&lt;0000465d&gt;] mangle_kernel_stack+0xcd/0xda
 [&lt;0008c00c&gt;] pcpu_balance_workfn+0xb2/0x40e
Code: 2200 7419 e4a9 e589 2841 d9fc 0000 1000 &lt;2414&gt; 7203 c282 7602 b681 6600 0096 0242 fe00 0482 0000 0000 e9c0 11c3 ed89 2642

There's no need to call ioremap() for the SWIM address range, as it lies
within the usual IO device region at 0x5000 0000, which has already been
mapped by head.S.

Remove the redundant ioremap() and iounmap() calls to fix the hang.

Cc: Laurent Vivier &lt;lvivier@redhat.com&gt;
Cc: stable@vger.kernel.org # v4.14+
Tested-by: Stan Johnson &lt;userm57@yahoo.com&gt;
Signed-off-by: Finn Thain &lt;fthain@telegraphics.com.au&gt;
Acked-by: Laurent Vivier &lt;lvivier@redhat.com&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
<entry>
<title>genhd: Rename get_disk() to get_disk_and_module()</title>
<updated>2018-02-26T16:48:42+00:00</updated>
<author>
<name>Jan Kara</name>
<email>jack@suse.cz</email>
</author>
<published>2018-02-26T12:01:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=3079c22ea815775837a4f389ce2f7e1e7b202e09'/>
<id>urn:sha1:3079c22ea815775837a4f389ce2f7e1e7b202e09</id>
<content type='text'>
Rename get_disk() to get_disk_and_module() to make sure what the
function does. It's not a great name but at least it is now clear that
put_disk() is not it's counterpart.

Signed-off-by: Jan Kara &lt;jack@suse.cz&gt;
Signed-off-by: Jens Axboe &lt;axboe@kernel.dk&gt;
</content>
</entry>
</feed>
