diff options
| author | Alberto Garcia <berto@igalia.com> | 2020-05-04 17:52:17 +0200 |
|---|---|---|
| committer | Kevin Wolf <kwolf@redhat.com> | 2020-05-08 13:26:35 +0200 |
| commit | e4d7019e1a81c61de6a925c3ac5bb6e62ea21b29 (patch) | |
| tree | 39cffe3992e3e0fe8ec3deb57cddc26d6853881b /tests/qemu-iotests/206.out | |
| parent | 5fc2b4f21811668c7cbbe907bdddab839fb50fe9 (diff) | |
| download | qemu-e4d7019e1a81c61de6a925c3ac5bb6e62ea21b29.zip qemu-e4d7019e1a81c61de6a925c3ac5bb6e62ea21b29.tar.gz qemu-e4d7019e1a81c61de6a925c3ac5bb6e62ea21b29.tar.bz2 | |
qcow2: Avoid integer wraparound in qcow2_co_truncate()
After commit f01643fb8b47e8a70c04bbf45e0f12a9e5bc54de 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>
Diffstat (limited to 'tests/qemu-iotests/206.out')
0 files changed, 0 insertions, 0 deletions