summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristoph Hellwig <hch@lst.de>2020-11-16 17:56:52 +0300
committerJens Axboe <axboe@kernel.dk>2020-11-16 18:34:14 +0300
commit99473d9db93a3bf557161373a1eb33d2873edd2e (patch)
treeeee30935a5fb26d5290cab43238b0f7edfd95a56
parente2b6b301871719d1db0b1ed7a1ed9e06750c80fc (diff)
downloadlinux-99473d9db93a3bf557161373a1eb33d2873edd2e.tar.xz
block: remove the call to __invalidate_device in check_disk_size_change
__invalidate_device without the kill_dirty parameter just invalidates various clean entries in caches, which doesn't really help us with anything, but can cause all kinds of horrible lock orders due to how it calls into the file system. The only reason this hasn't been a major issue is because so many people use partitions, for which no invalidation was performed anyway. Signed-off-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Jens Axboe <axboe@kernel.dk>
-rw-r--r--fs/block_dev.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 9e84b1928b94..66ebf594c97f 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -1334,12 +1334,6 @@ static void check_disk_size_change(struct gendisk *disk,
i_size_write(bdev->bd_inode, disk_size);
}
spin_unlock(&bdev->bd_size_lock);
-
- if (bdev_size > disk_size) {
- if (__invalidate_device(bdev, false))
- pr_warn("VFS: busy inodes on resized disk %s\n",
- disk->disk_name);
- }
}
/**