diff options
| author | Christoph Hellwig <hch@lst.de> | 2021-07-15 17:17:11 +0300 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2021-07-15 18:32:34 +0300 |
| commit | 05d69d950d9d84218fc9beafd02dea1f6a70e09e (patch) | |
| tree | 67cb04462645bc180be976d23a745d2e8c15831e /include | |
| parent | a347c153b15c06479986839beefabad15a7ea83d (diff) | |
| download | linux-05d69d950d9d84218fc9beafd02dea1f6a70e09e.tar.xz | |
xen-blkfront: sanitize the removal state machine
xen-blkfront has a weird protocol where close message from the remote
side can be delayed, and where hot removals are treated somewhat
differently from regular removals, all leading to potential NULL
pointer removals, and a del_gendisk from the block device release
method, which will deadlock. Fix this by just performing normal hot
removals even when the device is opened like all other Linux block
drivers.
Fixes: c76f48eb5c08 ("block: take bd_mutex around delete_partitions in del_gendisk")
Reported-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Tested-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Link: https://lore.kernel.org/r/20210715141711.1257293-1-hch@lst.de
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions