From: Jeff Layton <jlayton@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
fstests@vger.kernel.org, linux-nfs@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH fstests v2 3/3] generic/578: only run on filesystems that support FIEMAP
Date: Fri, 25 Aug 2023 10:57:20 -0400 [thread overview]
Message-ID: <bf82ceee8ed50e5767c4570e4ff3d02ec56fc3b0.camel@kernel.org> (raw)
In-Reply-To: <20230825141651.vd6lh3n4ztru5svl@zlang-mailbox>
On Fri, 2023-08-25 at 22:16 +0800, Zorro Lang wrote:
> On Thu, Aug 24, 2023 at 01:28:26PM -0400, Jeff Layton wrote:
> > On Thu, 2023-08-24 at 10:09 -0700, Darrick J. Wong wrote:
> > > On Thu, Aug 24, 2023 at 12:44:19PM -0400, Jeff Layton wrote:
> > > > Some filesystems (e.g. NFS) don't support FIEMAP. Limit generic/578 to
> > > > filesystems that do.
> > > >
> > > > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > > > ---
> > > > common/rc | 13 +++++++++++++
> > > > tests/generic/578 | 1 +
> > > > 2 files changed, 14 insertions(+)
> > > >
> > > > diff --git a/common/rc b/common/rc
> > > > index 33e74d20c28b..98d27890f6f7 100644
> > > > --- a/common/rc
> > > > +++ b/common/rc
> > > > @@ -3885,6 +3885,19 @@ _require_metadata_journaling()
> > > > fi
> > > > }
> > > >
> > > > +_require_fiemap()
> > > > +{
> > > > + local testfile=$TEST_DIR/fiemaptest.$$
> > > > +
> > > > + touch $testfile
> > > > + $XFS_IO_PROG -r -c "fiemap" $testfile 1>$testfile.out 2>&1
> > > > + if grep -q 'Operation not supported' $testfile.out; then
> > > > + _notrun "FIEMAP is not supported by this filesystem"
> > > > + fi
> > > > +
> > > > + rm -f $testfile $testfile.out
> > > > +}
> > >
> > > _require_xfs_io_command "fiemap" ?
> > >
> > >
> >
> > Ok, I figured we'd probably do this test after testing for that
> > separately, but you're correct that we do require it here.
> >
> > If we add that, should we also do this, at least in all of the general
> > tests?
> >
> > s/_require_xfs_io_command "fiemap"/_require_fiemap/
> >
> > I think we end up excluding some of those tests on NFS for other
> > reasons, but other filesystems that don't support fiemap might still try
> > to run these tests.
>
> We have lots of cases contains _require_xfs_io_command "fiemap", so I think
> we can keep this "tradition", don't bring a new _require_fiemap for now,
> so ...
>
> >
> > > > +
> > > > _count_extents()
> > > > {
> > > > $XFS_IO_PROG -r -c "fiemap" $1 | tail -n +2 | grep -v hole | wc -l
> > > > diff --git a/tests/generic/578 b/tests/generic/578
> > > > index b024f6ff90b4..903055b2ca58 100755
> > > > --- a/tests/generic/578
> > > > +++ b/tests/generic/578
> > > > @@ -26,6 +26,7 @@ _require_test_program "mmap-write-concurrent"
> > > > _require_command "$FILEFRAG_PROG" filefrag
> > > > _require_test_reflink
> > > > _require_cp_reflink
> > > > +_require_fiemap
>
> _require_xfs_io_command "fiemap"
>
That's not sufficient -- there is already a call to that in this test.
_require_xfs_io_command just validates that the xfs_io binary has
plumbing for that command (which just issues an ioctl to the file).
Even if the binary has support, the underlying filesystem has to support
the ioctl.
Many don't, so we need to test for that specifically.
> > > >
> > > > compare() {
> > > > for i in $(seq 1 8); do
> > > >
> > > > --
> > > > 2.41.0
> > > >
> >
> > --
> > Jeff Layton <jlayton@kernel.org>
> >
>
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-08-25 14:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 16:44 [PATCH fstests v2 0/3] fstests: add appropriate checks for fs features for some tests Jeff Layton
2023-08-24 16:44 ` [PATCH fstests v2 1/3] common/attr: fix the _require_acl test Jeff Layton
2023-08-24 16:44 ` [PATCH fstests v2 2/3] generic/513: limit to filesystems that support capabilities Jeff Layton
2023-08-25 14:11 ` Zorro Lang
2023-08-25 15:02 ` Jeff Layton
2023-08-27 12:45 ` Zorro Lang
2023-08-27 13:43 ` Jeff Layton
2023-08-28 14:35 ` Zorro Lang
2023-08-24 16:44 ` [PATCH fstests v2 3/3] generic/578: only run on filesystems that support FIEMAP Jeff Layton
2023-08-24 17:09 ` Darrick J. Wong
2023-08-24 17:28 ` Jeff Layton
2023-08-25 14:16 ` Zorro Lang
2023-08-25 14:57 ` Jeff Layton [this message]
2023-08-25 15:18 ` Darrick J. Wong
2023-08-25 17:34 ` Jeff Layton
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=bf82ceee8ed50e5767c4570e4ff3d02ec56fc3b0.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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;
as well as URLs for NNTP newsgroup(s).