diff options
author | Christoph Hellwig <hch@lst.de> | 2020-08-23 11:10:43 +0200 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2020-09-02 00:49:25 +0200 |
commit | c13f0fbc4c191aab5e95b01589ff5bbc6556e4f6 (patch) | |
tree | 68b5a06272126ff20e89f78fc147e8a3926d9f13 /block/blk-map.c | |
parent | block: fix locking for struct block_device size updates (diff) | |
download | linux-c13f0fbc4c191aab5e95b01589ff5bbc6556e4f6.tar.xz linux-c13f0fbc4c191aab5e95b01589ff5bbc6556e4f6.zip |
nvme: don't call revalidate_disk from nvme_set_queue_dying
In nvme_set_queue_dying we really just want to ensure the disk and bdev
sizes are set to zero. Going through revalidate_disk leads to a somewhat
arcance and complex callchain relying on special behavior in a few
places. Instead just lift the set_capacity directly to
nvme_set_queue_dying, and rename and move the nvme_mpath_update_disk_size
helper so that we can use it in nvme_set_queue_dying to propagate the
size to the bdev without detours.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Hannes Reinecke <hare@suse.de>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'block/blk-map.c')
0 files changed, 0 insertions, 0 deletions