Hi,
This is an alternative approach to changing null-co driver
default 'read-zeroes' option to true:
https://www.mail-archive.com/qemu-block@nongnu.org/msg80873.html
Instead we introduce yet another block driver with an explicit
name: 'zeroes-co'. We then clarify in secure-coding-practices.rst
that security reports have to be sent using this new driver.
The 2nd patch is RFC because I won't spend time converting the
tests until the first patch is discussed, as I already spent enough
time doing that in the previous mentioned series.
Regards,
Phil.
Philippe Mathieu-Daudé (3):
block: Introduce the 'zeroes-co' driver
tests/test-blockjob: Use zeroes-co instead of null-co,read-zeroes=on
docs/secure-coding-practices: Describe null-co/zeroes-co block drivers
docs/devel/secure-coding-practices.rst | 7 +
block/zeroes.c | 306 +++++++++++++++++++++++++
Why not add another BlockDriver struct to block/null.c and set the read_zeroes field in the .bdrv_file_open callback? It would make the patch much simpler.
Fam
tests/test-blockjob.c | 4 +-
block/meson.build | 1 +
4 files changed, 315 insertions(+), 3 deletions(-)
create mode 100644 block/zeroes.c
--
2.26.2