tag 14b0b2f76b2761b5f7c3954fe1b3917b1ae2b3fb
tagger Jens Axboe <axboe@kernel.dk> Fri May 01 10:28:11 2020 -0600
object 10c70d95c0f2f9a6f52d0e33243d2877370cef51

block-5.7-2020-05-01

commit 10c70d95c0f2f9a6f52d0e33243d2877370cef51
author Christoph Hellwig <hch@lst.de> Tue Apr 28 10:52:03 2020 +0200
committer Jens Axboe <axboe@kernel.dk> Thu Apr 30 10:25:43 2020 -0600
tree 6a0a7bb8aa945be7c521cbc1c93053ca9706b550
parent 47ed39e0625d3a47b6d6c0a12942b62fb802298f

block: remove the bd_openers checks in blk_drop_partitions

When replacing the bd_super check with a bd_openers I followed a logical
conclusion, which turns out to be utterly wrong.  When a block device has
bd_super sets it has a mount file system on it (although not every
mounted file system sets bd_super), but that also implies it doesn't even
have partitions to start with.

So instead of trying to come up with a logical check for all openers,
just remove the check entirely.

Fixes: d3ef5536274f ("block: fix busy device checking in blk_drop_partitions")
Fixes: cb6b771b05c3 ("block: fix busy device checking in blk_drop_partitions again")
Reported-by: Michal Koutný <mkoutny@suse.com>
Reported-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>