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>
Showing
- block.c 0 additions, 21 deletionsblock.c
- block/file-posix.c 0 additions, 1 deletionblock/file-posix.c
- block/file-win32.c 0 additions, 1 deletionblock/file-win32.c
- block/nfs.c 0 additions, 1 deletionblock/nfs.c
- block/qcow2.c 0 additions, 1 deletionblock/qcow2.c
- block/qed.c 0 additions, 1 deletionblock/qed.c
- block/raw-format.c 0 additions, 6 deletionsblock/raw-format.c
- block/rbd.c 0 additions, 1 deletionblock/rbd.c
- block/sheepdog.c 0 additions, 3 deletionsblock/sheepdog.c
- block/ssh.c 0 additions, 1 deletionblock/ssh.c
- include/block/block.h 0 additions, 1 deletioninclude/block/block.h
- include/block/block_int.h 0 additions, 7 deletionsinclude/block/block_int.h
Loading
Please register or sign in to comment