From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Zorro Lang <zlang@redhat.com>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: [PATCH] xfs: don't run tests that require v4 file systems when not supported
Date: Thu, 28 Mar 2024 08:05:42 -0700 [thread overview]
Message-ID: <20240328150542.GD6379@frogsfrogsfrogs> (raw)
In-Reply-To: <20240328145641.GA29197@lst.de>
On Thu, Mar 28, 2024 at 03:56:41PM +0100, Christoph Hellwig wrote:
> On Thu, Mar 28, 2024 at 09:59:05PM +0800, Zorro Lang wrote:
> > On Thu, Mar 28, 2024 at 01:17:49PM +0100, Christoph Hellwig wrote:
> > > Add a _require_xfs_nocrc helper that checks that we can mkfs and mount
> > > a crc=0 file systems before running tests that rely on it to avoid failures
> > > on kernels with CONFIG_XFS_SUPPORT_V4 disabled.
> > >
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > > ---
> >
> > This change makes sense to me, thanks for this update.
> > By searching "crc=0" in tests/xfs, I got x/096, x/078 and x/300 which
> > are not in this patch. Is there any reason about why they don't need it?
>
> xfs/078 only forces crc=0 for block size <= 1024 bytes. Would be
> kinds sad to disable it just to work around this case.
The crc=0 forcing case seems only to activate if
XFS_MKFS_HAS_NO_META_SUPPORT is non-empty, which happens only if
mkfs.xfs does /not/ support V5 filesystems. Maybe we can drop that
case?
> xfs/096 requires an obsolete mkfs without input validation, but
> I guess adding the doesn't hurt
Why do we even keep this test then? Do we care about xfsprogs 4.5?
4.19^H4 is the oldest LTS kernel...
--D
> xfs/300 needs the check, it doesn't run on my test setup because it
> requires selinux.
>
>
next prev parent reply other threads:[~2024-03-28 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 12:17 [PATCH] xfs: don't run tests that require v4 file systems when not supported Christoph Hellwig
2024-03-28 13:59 ` Zorro Lang
2024-03-28 14:56 ` Christoph Hellwig
2024-03-28 15:05 ` Darrick J. Wong [this message]
2024-03-28 17:09 ` Christoph Hellwig
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=20240328150542.GD6379@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-xfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.