From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Ma Xinjian <maxj.fnst@fujitsu.com>,
zlang@kernel.org, fstests@vger.kernel.org,
linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs/603: add _require_scrub
Date: Wed, 11 Jun 2025 07:18:11 -0700 [thread overview]
Message-ID: <20250611141811.GE6143@frogsfrogsfrogs> (raw)
In-Reply-To: <a3lsfm4pyryspt257eprspy6zapgkai5xubtcpxpw3edygurrn@7wfi73j2sbqt>
On Wed, Jun 11, 2025 at 02:50:11PM +0200, Carlos Maiolino wrote:
> On Tue, Jun 10, 2025 at 07:46:00AM -0700, Darrick J. Wong wrote:
> > On Tue, Jun 10, 2025 at 05:11:34PM +0800, Ma Xinjian wrote:
> > > From: Xinjian Ma <maxj.fnst@fujitsu.com>
> > >
> > > This test uses xfs_scrub which is an EXPERIMENTAL and unstable feature.
> > > Add _require_scrub to check if the system supports it.
> > >
> > > Signed-off-by: Xinjian Ma <maxj.fnst@fujitsu.com>
> >
> > Oops, thanks for the correction.
> > Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
>
> Experimental has meen removed from scrub in 6.16, is this still needed?
Yes, _require_scrub checks that the userspace driver program exists.
--D
> >
> > --D
> >
> > > ---
> > > tests/xfs/603 | 1 +
> > > 1 file changed, 1 insertion(+)
> > >
> > > diff --git a/tests/xfs/603 b/tests/xfs/603
> > > index 04122b55..d6058a3e 100755
> > > --- a/tests/xfs/603
> > > +++ b/tests/xfs/603
> > > @@ -20,6 +20,7 @@ _require_xfs_db_command iunlink
> > > # until after the directory repair code was merged
> > > _require_xfs_io_command repair -R directory
> > > _require_scratch_nocheck # repair doesn't like single-AG fs
> > > +_require_scrub
> > >
> > > # From the AGI definition
> > > XFS_AGI_UNLINKED_BUCKETS=64
> > > --
> > > 2.49.0
> > >
> > >
> >
>
prev parent reply other threads:[~2025-06-11 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 9:11 [PATCH] xfs/603: add _require_scrub Ma Xinjian
2025-06-10 14:46 ` Darrick J. Wong
2025-06-11 12:50 ` Carlos Maiolino
2025-06-11 14:18 ` Darrick J. Wong [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=20250611141811.GE6143@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=cem@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=maxj.fnst@fujitsu.com \
--cc=zlang@kernel.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