aboutsummaryrefslogtreecommitdiff
path: root/block/file-win32.c
diff options
context:
space:
mode:
authorEric Blake <eblake@redhat.com>2020-04-28 15:29:05 -0500
committerKevin Wolf <kwolf@redhat.com>2020-05-08 13:26:35 +0200
commit47e0b38a13935cb666f88964c3096654092f42d6 (patch)
treedb26706712a4f9db926275ffa5a52a88b63a2a3e /block/file-win32.c
parentdbc636e791ad04b6bcdec982d2b9c45d7182e037 (diff)
downloadqemu-47e0b38a13935cb666f88964c3096654092f42d6.zip
qemu-47e0b38a13935cb666f88964c3096654092f42d6.tar.gz
qemu-47e0b38a13935cb666f88964c3096654092f42d6.tar.bz2
block: Drop unused .bdrv_has_zero_init_truncate
Now that there are no clients of bdrv_has_zero_init_truncate, none of the drivers need to worry about providing it. What's more, this eliminates a source of some confusion: a literal reading of the documentation as written in ceaca56f and implemented in commit 1dcaf527 claims that a driver which returns 0 for bdrv_has_zero_init_truncate() must not return 1 for bdrv_has_zero_init(); this condition was violated for parallels, qcow, and sometimes for vdi, although in practice it did not matter since those drivers also lacked .bdrv_co_truncate. Signed-off-by: Eric Blake <eblake@redhat.com> Message-Id: <20200428202905.770727-10-eblake@redhat.com> Acked-by: Richard W.M. Jones <rjones@redhat.com> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
Diffstat (limited to 'block/file-win32.c')
-rw-r--r--block/file-win32.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/block/file-win32.c b/block/file-win32.c
index fa56968..221aaf7 100644
--- a/block/file-win32.c
+++ b/block/file-win32.c
@@ -641,7 +641,6 @@ BlockDriver bdrv_file = {
.bdrv_close = raw_close,
.bdrv_co_create_opts = raw_co_create_opts,
.bdrv_has_zero_init = bdrv_has_zero_init_1,
- .bdrv_has_zero_init_truncate = bdrv_has_zero_init_1,
.bdrv_aio_preadv = raw_aio_preadv,
.bdrv_aio_pwritev = raw_aio_pwritev,