revalidate_disk_size just updates the block device size from the disk
size. Thus calling it from revalidate_disk_size doesn't actually do
anything.
Signed-off-by: Christoph Hellwig
---
drivers/block/virtio_blk.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/block/virtio_blk.c b/dri
revalidate_disk_size just updates the block device size from the disk
size. Thus calling it from virtblk_update_cache_mode doesn't actually
do anything.
Signed-off-by: Christoph Hellwig
Acked-by: Stefan Hajnoczi
Acked-by: Michael S. Tsirkin
---
drivers/block/virtio_blk.c | 1 -
1 file changed
On 06/11/20 20:03, Christoph Hellwig wrote:
revalidate_disk_size just updates the block device size from the disk
size. Thus calling it from revalidate_disk_size doesn't actually do
s/revalidate_disk_size/virtblk_update_cache_mode/
anything.
--
dm-devel mailing list
dm-devel@redhat.com
htt
On Fri, Nov 06, 2020 at 08:03:35PM +0100, Christoph Hellwig wrote:
> revalidate_disk_size just updates the block device size from the disk
> size. Thus calling it from revalidate_disk_size doesn't actually do
> anything.
>
> Signed-off-by: Christoph Hellwig
> ---
> drivers/block/virtio_blk.c |
On Fri, Nov 06, 2020 at 08:03:35PM +0100, Christoph Hellwig wrote:
> revalidate_disk_size just updates the block device size from the disk
> size. Thus calling it from revalidate_disk_size doesn't actually do
> anything.
>
> Signed-off-by: Christoph Hellwig
Acked-by: Michael S. Tsirkin
> ---
