Hi, Cover letter from v1: https://lists.nongnu.org/archive/html/qemu-block/2022-01/msg00314.html
In v2, I’ve added a comment to the new test explaining why we need to pass --allocation-depth to qemu-nbd, as requested by Nir; and as he has implied, using the short options is kind of silly because they are anything but self-explanatory, so in v2, I’ve switched to exclusively using long options for the qemu-nbd invocation. (Also, added “Cc: qemu-stable” tag in patch 1.) git-backport-diff against v1: Key: [----] : patches are identical [####] : number of functional differences between upstream/downstream patch [down] : patch is downstream-only The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively 001/2:[----] [--] 'block/io: Update BSC only if want_zero is true' 002/2:[0013] [FC] 'iotests/block-status-cache: New test' Hanna Reitz (2): block/io: Update BSC only if want_zero is true iotests/block-status-cache: New test block/io.c | 6 +- tests/qemu-iotests/tests/block-status-cache | 139 ++++++++++++++++++ .../qemu-iotests/tests/block-status-cache.out | 5 + 3 files changed, 149 insertions(+), 1 deletion(-) create mode 100755 tests/qemu-iotests/tests/block-status-cache create mode 100644 tests/qemu-iotests/tests/block-status-cache.out -- 2.33.1
