From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH for-2.11] iotests: Fix 176 on 32-bit host
Date: Mon, 20 Nov 2017 21:55:29 +0100 [thread overview]
Message-ID: <0ec6d36c-c576-f184-19da-7ddf8ff1f11e@redhat.com> (raw)
In-Reply-To: <20171117190422.23626-1-eblake@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1678 bytes --]
On 2017-11-17 20:04, Eric Blake wrote:
> The contents of a qcow2 bitmap are rounded up to a size that
> matches the number of bits available for the granularity, but
> that granularity differs for 32-bit hosts (our default 64k
> cluster allows for 2M bitmap coverage per 'long') and 64-bit
> hosts (4M bitmap per 'long'). If the image is a multiple of
> 2M but not 4M, then the number of bytes occupied by the array
> of longs in memory differs between architecture, thus
> resulting in different SHA256 hashes.
>
> Furthermore (but untested by me), if our computation of the
> SHA256 hash is at all endian-dependent because of how we store
> data in memory, that's another variable we'd have to account
> for (ideally, we specified the bitmap stored in qcow2 as
> fixed-endian on disk, because the same qcow2 file must be
> usable across any architecture; but that says nothing about
> how we represent things in memory). But we already have test
> 165 to validate that bitmaps are stored correctly on disk,
> while this test is merely testing that the bitmap exists.
>
> So for this test, the easiest solution is to filter out the
> actual hash value. Broken in commit 4096974e.
>
> Reported-by: Max Reitz <mreitz@redhat.com>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
> tests/qemu-iotests/176 | 3 ++-
> tests/qemu-iotests/176.out | 8 ++++----
> 2 files changed, 6 insertions(+), 5 deletions(-)
Now that I've failed to keep my tree empty anyway:
Thanks, applied to my block branch:
https://github.com/XanClic/qemu/commits/block
(No offense taken if **someone** *cough* *cough* were to take it from me)
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2017-11-20 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 19:04 [Qemu-devel] [PATCH for-2.11] iotests: Fix 176 on 32-bit host Eric Blake
2017-11-17 19:10 ` Eric Blake
2017-11-17 22:59 ` [Qemu-devel] [Qemu-block] " John Snow
2017-11-20 20:36 ` Eric Blake
2017-11-20 20:27 ` [Qemu-devel] " Max Reitz
2017-11-20 20:55 ` Max Reitz [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=0ec6d36c-c576-f184-19da-7ddf8ff1f11e@redhat.com \
--to=mreitz@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@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).