From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/3] iotests: Fix 125
Date: Fri, 27 Sep 2019 11:29:44 +0200 [thread overview]
Message-ID: <db32c2d6-ff45-f651-bc90-ef3d4c79d5eb@redhat.com> (raw)
In-Reply-To: <20190925183231.11196-1-mreitz@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1570 bytes --]
On 25.09.19 20:32, Max Reitz wrote:
> Hi,
>
> iotest 125 is very broken. It uses qemu-img info’s “disk size” to
> determine an image’s on-disk size, but it does so in a wrong way: It
> just fetches the first number ([0-9]+), but that isn’t very useful
> because qemu-img info emits human-readable values that include units and
> decimal points.
>
> We should ust stat -c %b instead. That’s done in patch 3.
> Unfortunately, doing so exposed more problems.
>
> Patch 1 fixes a stupid bug in the test itself that we never noticed
> because of what patch 3 fixes. (Pull patch 3 before patch 1 and you’ll
> see.)
>
> The other thing is actually a bug in XFS. Its fallocate()
> implementation rounds up the length independently of the offset, so if
> you try to fallocate an unaligned range, chances are that it might not
> allocate the last block your range touches. Patch 2 detects that case
> and skips the test then. (Pull patch 3 before patch 2 and you’ll see
> the test fail on XFS.)
>
>
> Max Reitz (3):
> iotests: Fix 125 for growth_mode = metadata
> iotests: Disable 125 on broken XFS versions
> iotests: Use stat -c %b in 125
>
> tests/qemu-iotests/125 | 45 +++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 42 insertions(+), 3 deletions(-)
Thanks for the review, applied to my block branch:
https://git.xanclic.moe/XanClic/qemu/commits/branch/block
And for the record, I’ve sent a patch to the XFS driver:
https://www.spinics.net/lists/linux-xfs/msg32174.html
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-09-27 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-25 18:32 [PATCH 0/3] iotests: Fix 125 Max Reitz
2019-09-25 18:32 ` [PATCH 1/3] iotests: Fix 125 for growth_mode = metadata Max Reitz
2019-09-25 21:29 ` Eric Blake
2019-09-25 18:32 ` [PATCH 2/3] iotests: Disable 125 on broken XFS versions Max Reitz
2019-09-25 21:28 ` Eric Blake
2019-09-26 10:58 ` Max Reitz
2019-09-25 18:32 ` [PATCH 3/3] iotests: Use stat -c %b in 125 Max Reitz
2019-09-25 21:31 ` Eric Blake
2019-09-27 9:29 ` 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=db32c2d6-ff45-f651-bc90-ef3d4c79d5eb@redhat.com \
--to=mreitz@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).