From: Eric Blake <eblake@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] iotests/197: Fix for compat=0.10
Date: Mon, 27 Jul 2020 09:14:50 -0500 [thread overview]
Message-ID: <c9bf6fff-a78a-e160-58be-5a8cb87549f9@redhat.com> (raw)
In-Reply-To: <20200727135237.1096841-1-mreitz@redhat.com>
On 7/27/20 8:52 AM, Max Reitz wrote:
> Writing zeroes to a qcow2 v2 images without a backing file results in an
> unallocated cluster as of 61b3043965. 197 has a test for COR-ing a
> cluster on an image without a backing file, which means that the data
> will be zero, so now on a v2 image that cluster will just stay
> unallocated, and so the test fails. Just force compat=1.1 for that
> particular case to enforce the cluster to get allocated.
>
> Fixes: 61b3043965fe3552ee2684a97e7cc809ca7a71b3
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> tests/qemu-iotests/197 | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/tests/qemu-iotests/197 b/tests/qemu-iotests/197
> index 95f05b0e34..121959a09c 100755
> --- a/tests/qemu-iotests/197
> +++ b/tests/qemu-iotests/197
> @@ -112,7 +112,9 @@ echo
> echo '=== Partial final cluster ==='
> echo
>
> -_make_test_img 1024
> +# Force compat=1.1, because writing zeroes on a v2 image without a
> +# backing file would just result in an unallocated cluster
> +_make_test_img -o compat=1.1 1024
> $QEMU_IO -f $IMGFMT -C -c 'read 0 1024' "$TEST_IMG" | _filter_qemu_io
> $QEMU_IO -f $IMGFMT -c map "$TEST_IMG"
> _check_test_img
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
prev parent reply other threads:[~2020-07-27 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 13:52 [PATCH] iotests/197: Fix for compat=0.10 Max Reitz
2020-07-27 14:14 ` Eric Blake [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c9bf6fff-a78a-e160-58be-5a8cb87549f9@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).