qcow2: Limit total allocation range to INT_MAX

[PATCH 0/2] qcow2: Limit total allocation range to INT_MAX

Max Reitz posted 2 patches 4 years, 7 months ago

Download series mbox

Test asan passed

Test checkpatch passed

Test FreeBSD passed

Test docker-mingw@fedora passed

Test docker-clang@ubuntu passed

Test docker-quick@centos7 passed

Patches applied successfully (tree, apply log)
git fetch https://github.com/patchew-project/qemu tags/patchew/20191010100858.1261-1-mreitz@redhat.com

Maintainers: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>

block/qcow2-cluster.c      |  5 ++-
tests/qemu-iotests/268     | 83 ++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/268.out |  9 +++++
tests/qemu-iotests/group   |  1 +
4 files changed, 97 insertions(+), 1 deletion(-)
create mode 100755 tests/qemu-iotests/268
create mode 100644 tests/qemu-iotests/268.out

Expand all Fold all

[PATCH 0/2] qcow2: Limit total allocation range to INT_MAX

Posted by Max Reitz 4 years, 7 months ago

Hi,

While looking for why handle_alloc_space() seems to cause issues on
ppc64le+XFS (performance degradation and data corruption), I spotted
this other issue.  It isn’t as bad, but still needs fixing.

See patch 1 for what is fixed and patch 2 for what breaks otherwise.


Max Reitz (2):
  qcow2: Limit total allocation range to INT_MAX
  iotests: Test large write request to qcow2 file

 block/qcow2-cluster.c      |  5 ++-
 tests/qemu-iotests/268     | 83 ++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/268.out |  9 +++++
 tests/qemu-iotests/group   |  1 +
 4 files changed, 97 insertions(+), 1 deletion(-)
 create mode 100755 tests/qemu-iotests/268
 create mode 100644 tests/qemu-iotests/268.out

-- 
2.21.0

Re: [PATCH 0/2] qcow2: Limit total allocation range to INT_MAX

Posted by Kevin Wolf 4 years, 6 months ago

Am 10.10.2019 um 12:08 hat Max Reitz geschrieben:
> Hi,
> 
> While looking for why handle_alloc_space() seems to cause issues on
> ppc64le+XFS (performance degradation and data corruption), I spotted
> this other issue.  It isn’t as bad, but still needs fixing.
> 
> See patch 1 for what is fixed and patch 2 for what breaks otherwise.

Thanks, applied to the block branch.

Kevin