From: Bill O'Donnell <bodonnel@redhat.com>
To: Bill O'Donnell <bodonnel@redhat.com>
Cc: Zorro Lang <zlang@redhat.com>,
fstests@vger.kernel.org, quwenruo.btrfs@gmx.com,
esandeen@redhat.com
Subject: Re: [PATCH v2] fstests: generic/353 should accomodate other pwrite behaviors
Date: Mon, 23 Oct 2023 17:40:31 -0500 [thread overview]
Message-ID: <ZTb2Xy4vTi6/RGQo@redhat.com> (raw)
In-Reply-To: <ZRbUQveXYWjhlvAN@redhat.com>
ping?
On Fri, Sep 29, 2023 at 08:42:26AM -0500, Bill O'Donnell wrote:
> On Fri, Sep 29, 2023 at 01:06:51PM +0800, Zorro Lang wrote:
> > On Fri, Sep 01, 2023 at 11:18:16AM -0500, Bill O'Donnell wrote:
> > > xfs_io pwrite issues a series of block size writes, but there is no
> > > guarantee that the resulting extent(s) will be singular or contiguous.
> > > This behavior is acceptable, but the test is flawed in that it expects
> > > a single extent for a pwrite.
> > >
> > > Modify test to use actual blocksize for pwrite and reflink. Also
> > > modify it to accommodate pwrite and reflink that produce different
> > > mapping results.
> > >
> > > Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
> > > ---
> >
> > This patch makes sense to me, but this case looks like a regression test
> > test for a known btrfs issue. But this test case doesn't point out which
> > bug/fix does it test for. So I don't know if the 64k blocksize is a
> > necessary condition to reproduce the bug.
> >
> > If we can prove it still can reproduce that bug with this patch at least,
> > then it's good to me to merge it.
>
> I'd like Qu to weigh in on this from the btrfs standpoint.
>
> Thanks-
> Bill
>
> >
> > Thanks,
> > Zorro
> >
> > > tests/generic/353 | 29 ++++++++++++++++-------------
> > > tests/generic/353.out | 15 +--------------
> > > 2 files changed, 17 insertions(+), 27 deletions(-)
> > >
> > > diff --git a/tests/generic/353 b/tests/generic/353
> > > index 9a1471bd..c5639725 100755
> > > --- a/tests/generic/353
> > > +++ b/tests/generic/353
> > > @@ -29,31 +29,34 @@ _require_xfs_io_command "fiemap"
> > > _scratch_mkfs > /dev/null 2>&1
> > > _scratch_mount
> > >
> > > -blocksize=64k
> > > +blocksize=$(_get_file_block_size $SCRATCH_MNT)
> > > +
> > > file1="$SCRATCH_MNT/file1"
> > > file2="$SCRATCH_MNT/file2"
> > > +extmap1="$SCRATCH_MNT/extmap1"
> > > +extmap2="$SCRATCH_MNT/extmap2"
> > >
> > > # write the initial file
> > > -_pwrite_byte 0xcdcdcdcd 0 $blocksize $file1 | _filter_xfs_io
> > > +_pwrite_byte 0xcdcdcdcd 0 $blocksize $file1 > /dev/null
> > >
> > > # reflink initial file
> > > -_reflink_range $file1 0 $file2 0 $blocksize | _filter_xfs_io
> > > +_reflink_range $file1 0 $file2 0 $blocksize > /dev/null
> > >
> > > # check their fiemap to make sure it's correct
> > > -echo "before sync:"
> > > -echo "$file1" | _filter_scratch
> > > -$XFS_IO_PROG -c "fiemap -v" $file1 | _filter_fiemap_flags
> > > -echo "$file2" | _filter_scratch
> > > -$XFS_IO_PROG -c "fiemap -v" $file2 | _filter_fiemap_flags
> > > +$XFS_IO_PROG -c "fiemap -v" $file1 | _filter_fiemap_flags > $extmap1
> > > +$XFS_IO_PROG -c "fiemap -v" $file2 | _filter_fiemap_flags > $extmap2
> > > +
> > > +cmp -s $extmap1 $extmap2 || echo "mismatched extent maps before sync"
> > >
> > > # sync and recheck, to make sure the fiemap doesn't change just
> > > # due to sync
> > > sync
> > > -echo "after sync:"
> > > -echo "$file1" | _filter_scratch
> > > -$XFS_IO_PROG -c "fiemap -v" $file1 | _filter_fiemap_flags
> > > -echo "$file2" | _filter_scratch
> > > -$XFS_IO_PROG -c "fiemap -v" $file2 | _filter_fiemap_flags
> > > +$XFS_IO_PROG -c "fiemap -v" $file1 | _filter_fiemap_flags > $extmap1
> > > +$XFS_IO_PROG -c "fiemap -v" $file2 | _filter_fiemap_flags > $extmap2
> > > +
> > > +cmp -s $extmap1 $extmap2 || echo "mismatched extent maps after sync"
> > > +
> > > +echo "Silence is golden"
> > >
> > > # success, all done
> > > status=0
> > > diff --git a/tests/generic/353.out b/tests/generic/353.out
> > > index 4f6e0b92..16ba4f1f 100644
> > > --- a/tests/generic/353.out
> > > +++ b/tests/generic/353.out
> > > @@ -1,15 +1,2 @@
> > > QA output created by 353
> > > -wrote 65536/65536 bytes at offset 0
> > > -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > > -linked 65536/65536 bytes at offset 0
> > > -XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> > > -before sync:
> > > -SCRATCH_MNT/file1
> > > -0: [0..127]: shared|last
> > > -SCRATCH_MNT/file2
> > > -0: [0..127]: shared|last
> > > -after sync:
> > > -SCRATCH_MNT/file1
> > > -0: [0..127]: shared|last
> > > -SCRATCH_MNT/file2
> > > -0: [0..127]: shared|last
> > > +Silence is golden
> > > --
> > > 2.41.0
> > >
> >
>
next prev parent reply other threads:[~2023-10-23 22:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 16:18 [PATCH v2] fstests: generic/353 should accomodate other pwrite behaviors Bill O'Donnell
2023-09-08 13:42 ` Bill O'Donnell
2023-09-21 22:30 ` Bill O'Donnell
2023-09-25 20:37 ` Bill O'Donnell
2023-09-29 5:06 ` Zorro Lang
2023-09-29 13:42 ` Bill O'Donnell
2023-10-23 22:40 ` Bill O'Donnell [this message]
2023-10-24 5:21 ` Zorro Lang
2023-10-24 7:03 ` Qu Wenruo
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=ZTb2Xy4vTi6/RGQo@redhat.com \
--to=bodonnel@redhat.com \
--cc=esandeen@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=zlang@redhat.com \
/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