From: "Darrick J. Wong" <djwong@kernel.org>
To: John Garry <john.g.garry@oracle.com>
Cc: zlang@redhat.com, fstests@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 7/7] generic/774: turn off lfsr
Date: Wed, 12 Nov 2025 10:15:33 -0800 [thread overview]
Message-ID: <20251112181533.GE196366@frogsfrogsfrogs> (raw)
In-Reply-To: <8d9dc58f-ba64-4abe-91b9-251636527a65@oracle.com>
On Tue, Nov 11, 2025 at 09:01:59AM +0000, John Garry wrote:
> On 10/11/2025 18:27, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> >
> > This test fails mostly-predictably across my testing fleet with:
> >
> > --- /run/fstests/bin/tests/generic/774.out 2025-10-20 10:03:43.432910446 -0700
> > +++ /var/tmp/fstests/generic/774.out.bad 2025-11-10 01:14:58.941775866 -0800
> > @@ -1,2 +1,11 @@
> > QA output created by 774
> > +fio: failed initializing LFSR
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 0, length 33554432 (requested block: offset=0, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 33554432, length 33554432 (requested block: offset=33554432, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 67108864, length 33554432 (requested block: offset=67108864, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 100663296, length 33554432 (requested block: offset=100663296, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 134217728, length 33554432 (requested block: offset=134217728, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 167772160, length 33554432 (requested block: offset=167772160, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 201326592, length 33554432 (requested block: offset=201326592, length=33554432)
> > +verify: bad magic header 0, wanted acca at file /opt/test-file offset 234881024, length 33554432 (requested block: offset=234881024, length=33554432)
> > Silence is golden
> >
> > I'm not sure why the linear feedback shift register algorithm is
> > specifically needed for this test.
> >
> > Cc: <fstests@vger.kernel.org> # v2025.10.20
> > Fixes: 9117fb93b41c38 ("generic: Add atomic write test using fio verify on file mixed mappings")
> > Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
>
> Reviewed-by: John Garry <john.g.garry@oracle.com>
>
> BTW, if you would like to make further tidy ups, then I don't think that
> verify_write_sequence=0 is required (for verify config). That is only
> relevant when we have multiple threads writing to the same region, which I
> don't think is the case here.
No I would not. Send a separate patch with a separate justification
please.
--D
> cheers
>
> > ---
> > tests/generic/774 | 4 ----
> > 1 file changed, 4 deletions(-)
> >
> >
> > diff --git a/tests/generic/774 b/tests/generic/774
> > index 28886ed5b09ff7..86ab01fbd35874 100755
> > --- a/tests/generic/774
> > +++ b/tests/generic/774
> > @@ -56,14 +56,12 @@ group_reporting=1
> > ioengine=libaio
> > rw=randwrite
> > io_size=$((filesize/3))
> > -random_generator=lfsr
> > # Create unwritten extents
> > [prep_unwritten_blocks]
> > ioengine=falloc
> > rw=randwrite
> > io_size=$((filesize/3))
> > -random_generator=lfsr
> > EOF
> > cat >$fio_aw_config <<EOF
> > @@ -73,7 +71,6 @@ ioengine=libaio
> > rw=randwrite
> > direct=1
> > atomic=1
> > -random_generator=lfsr
> > group_reporting=1
> > filename=$testfile
> > @@ -93,7 +90,6 @@ cat >$fio_verify_config <<EOF
> > [verify_job]
> > ioengine=libaio
> > rw=read
> > -random_generator=lfsr
> > group_reporting=1
> > filename=$testfile
> >
>
>
next prev parent reply other threads:[~2025-11-12 18:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 18:26 [PATCHSET] fstests: more random fixes for v2025.11.04 Darrick J. Wong
2025-11-10 18:26 ` [PATCH 1/7] common: leave any breadcrumbs when _link_out_file_named can't find the output file Darrick J. Wong
2025-11-11 9:13 ` Christoph Hellwig
2025-11-10 18:26 ` [PATCH 2/7] generic/778: fix severe performance problems Darrick J. Wong
2025-11-11 9:27 ` Christoph Hellwig
2025-11-13 11:53 ` Ojaswin Mujoo
2025-11-15 2:32 ` Darrick J. Wong
2025-11-29 8:52 ` Ojaswin Mujoo
2025-12-01 23:19 ` Darrick J. Wong
2025-12-03 6:19 ` Ojaswin Mujoo
2025-12-04 17:18 ` Darrick J. Wong
2025-11-10 18:26 ` [PATCH 3/7] generic/778: fix background loop control with sentinel files Darrick J. Wong
2025-11-11 9:28 ` Christoph Hellwig
2025-11-13 11:06 ` Ojaswin Mujoo
2025-11-10 18:27 ` [PATCH 4/7] generic/019: skip test when there is no journal Darrick J. Wong
2025-11-11 9:28 ` Christoph Hellwig
2025-11-12 18:20 ` Darrick J. Wong
2025-11-10 18:27 ` [PATCH 5/7] xfs/837: fix test to work with pre-metadir quota mount options Darrick J. Wong
2025-11-11 9:29 ` Christoph Hellwig
2025-11-10 18:27 ` [PATCH 6/7] generic/774: reduce file size Darrick J. Wong
2025-11-11 9:13 ` John Garry
2025-11-11 9:29 ` Christoph Hellwig
2025-11-11 9:31 ` Christoph Hellwig
2025-11-12 18:05 ` Darrick J. Wong
2025-11-13 10:44 ` Ojaswin Mujoo
2025-11-10 18:27 ` [PATCH 7/7] generic/774: turn off lfsr Darrick J. Wong
2025-11-11 9:01 ` John Garry
2025-11-12 18:15 ` Darrick J. Wong [this message]
2025-11-11 9:32 ` Christoph Hellwig
2025-11-13 10:34 ` Ojaswin Mujoo
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=20251112181533.GE196366@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=john.g.garry@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--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