summaryrefslogtreecommitdiff
path: root/kernel/async.c
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2013-01-02 15:37:17 +1030
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2013-01-27 20:49:00 -0800
commit00112dc1bf0af8f50cd7f7c8008eb4230e8db5d7 (patch)
tree7cc0137ea131f549cbf297dee14516688f7ff663 /kernel/async.c
parenta833765edd399f4c14337592bd13df6a83094c5a (diff)
virtio-blk: Don't free ida when disk is in use
commit f4953fe6c4aeada2d5cafd78aa97587a46d2d8f9 upstream. 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> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'kernel/async.c')
0 files changed, 0 insertions, 0 deletions