diff options
author | Anthony Iliopoulos <ailiopoulos@suse.com> | 2019-07-29 14:40:40 +0200 |
---|---|---|
committer | Christoph Hellwig <hch@lst.de> | 2019-07-30 13:29:20 +0300 |
commit | fab7772bfbcfe8fb8e3e352a6a8fcaf044cded17 (patch) | |
tree | da774080df888f4bfabb6687f1f0163d90737595 | |
parent | 71d6c505b4d9e6f76586350450e785e3d452b346 (diff) | |
download | linux-stable-fab7772bfbcfe8fb8e3e352a6a8fcaf044cded17.tar.gz linux-stable-fab7772bfbcfe8fb8e3e352a6a8fcaf044cded17.tar.bz2 linux-stable-fab7772bfbcfe8fb8e3e352a6a8fcaf044cded17.zip |
nvme-multipath: revalidate nvme_ns_head gendisk in nvme_validate_ns
When CONFIG_NVME_MULTIPATH is set, only the hidden gendisk associated
with the per-controller ns is run through revalidate_disk when a
rescan is triggered, while the visible blockdev never gets its size
(bdev->bd_inode->i_size) updated to reflect any capacity changes that
may have occurred.
This prevents online resizing of nvme block devices and in extension of
any filesystems atop that will are unable to expand while mounted, as
userspace relies on the blockdev size for obtaining the disk capacity
(via BLKGETSIZE/64 ioctls).
Fix this by explicitly revalidating the actual namespace gendisk in
addition to the per-controller gendisk, when multipath is enabled.
Signed-off-by: Anthony Iliopoulos <ailiopoulos@suse.com>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Reviewed-by: Johannes Thumshirn <jthumshirn@suse.de>
Signed-off-by: Christoph Hellwig <hch@lst.de>
-rw-r--r-- | drivers/nvme/host/core.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/nvme/host/core.c b/drivers/nvme/host/core.c index 8f3fbe5ca937..80c7a7ee240b 100644 --- a/drivers/nvme/host/core.c +++ b/drivers/nvme/host/core.c @@ -1715,6 +1715,7 @@ static void __nvme_revalidate_disk(struct gendisk *disk, struct nvme_id_ns *id) if (ns->head->disk) { nvme_update_disk_info(ns->head->disk, ns, id); blk_queue_stack_limits(ns->head->disk->queue, ns->queue); + revalidate_disk(ns->head->disk); } #endif } |