diff options
| author | Alexander Graf <agraf@suse.de> | 2013-01-02 09:07:17 +0400 |
|---|---|---|
| committer | Rusty Russell <rusty@rustcorp.com.au> | 2013-01-02 09:07:58 +0400 |
| commit | f4953fe6c4aeada2d5cafd78aa97587a46d2d8f9 (patch) | |
| tree | 25dea7884cb125d2c0f76a38938eb624c94ec228 /kernel/module.c | |
| parent | a7f2a366f62319dfebf8d4dfe8b211f631c78457 (diff) | |
| download | linux-f4953fe6c4aeada2d5cafd78aa97587a46d2d8f9.tar.xz | |
virtio-blk: Don't free ida when disk is in use
When a file system is mounted on a virtio-blk disk, we then remove it
and then reattach it, the reattached disk gets the same disk name and
ids as the hot removed one.
This leads to very nasty effects - mostly rendering the newly attached
device completely unusable.
Trying what happens when I do the same thing with a USB device, I saw
that the sd node simply doesn't get free'd when a device gets forcefully
removed.
Imitate the same behavior for vd devices. This way broken vd devices
simply are never free'd and newly attached ones keep working just fine.
Signed-off-by: Alexander Graf <agraf@suse.de>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Cc: stable@kernel.org
Diffstat (limited to 'kernel/module.c')
0 files changed, 0 insertions, 0 deletions