e4d7019e1a
After commit f01643fb8b when an image is
extended and BDRV_REQ_ZERO_WRITE is set then the new clusters are
zeroized.
The code however does not detect correctly situations when the old and
the new end of the image are within the same cluster. The problem can
be reproduced with these steps:
qemu-img create -f qcow2 backing.qcow2 1M
qemu-img create -f qcow2 -F qcow2 -b backing.qcow2 top.qcow2
qemu-img resize --shrink top.qcow2 520k
qemu-img resize top.qcow2 567k
In the last step offset - zero_start causes an integer wraparound.
Signed-off-by: Alberto Garcia <berto@igalia.com>
Message-Id: <20200504155217.10325-1-berto@igalia.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
25 lines
1,013 B
Plaintext
25 lines
1,013 B
Plaintext
QA output created by 292
|
|
### Create the backing image
|
|
Formatting 'TEST_DIR/t.IMGFMT.base', fmt=IMGFMT size=1048576
|
|
### Fill the backing image with data (0x11)
|
|
wrote 1048576/1048576 bytes at offset 0
|
|
1 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
### Create the top image
|
|
Formatting 'TEST_DIR/t.IMGFMT', fmt=IMGFMT size=1048576 backing_file=TEST_DIR/t.IMGFMT.base backing_fmt=IMGFMT
|
|
### Fill the top image with data (0x22)
|
|
wrote 1048576/1048576 bytes at offset 0
|
|
1 MiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
### Shrink the image to 520k
|
|
Image resized.
|
|
### Grow the image to 567k
|
|
Image resized.
|
|
### Check that the tail of the image reads as zeroes
|
|
read 532480/532480 bytes at offset 0
|
|
520 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
read 48128/48128 bytes at offset 532480
|
|
47 KiB, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
|
|
### Show output of qemu-img map
|
|
Offset Length Mapped to File
|
|
0 0x8dc00 0x50000 TEST_DIR/t.qcow2
|
|
*** done
|