From: "Darrick J. Wong" <djwong@kernel.org>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/726,727: add missing _require_scratch_reflink
Date: Fri, 17 Nov 2023 14:09:45 -0800 [thread overview]
Message-ID: <20231117220945.GH36175@frogsfrogsfrogs> (raw)
In-Reply-To: <20231117145155.t7vvq3ksdrhyo5ff@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Fri, Nov 17, 2023 at 10:51:55PM +0800, Zorro Lang wrote:
> On Wed, Nov 08, 2023 at 04:24:28PM +0100, Christoph Hellwig wrote:
> > These two tests require reflink functionality, add the correct
> > statement to ensure that.
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > tests/generic/726 | 2 ++
> > tests/generic/727 | 2 ++
> > 2 files changed, 4 insertions(+)
> >
> > diff --git a/tests/generic/726 b/tests/generic/726
> > index f0d8df2e..77afe10c 100755
> > --- a/tests/generic/726
> > +++ b/tests/generic/726
> > @@ -19,6 +19,7 @@ _begin_fstest auto fiexchange swapext quick
> >
> > # Import common functions.
> > . ./common/filter
> > +. ./common/reflink
> >
> > # real QA test starts here
> >
> > @@ -28,6 +29,7 @@ _require_user
> > _require_xfs_io_command swapext '-v vfs -a'
> > _require_xfs_io_command startupdate
> > _require_scratch
> > +_require_scratch_reflink
>
> Does the "startupdate" actually need reflink feature?
It does, but the -a switch to the _require_xfs_io_command swapext line
above will fail _notrun the test. Or at least it would had I not
changed the CLI options when I gave up on getting FIEXCHANGE merged and
reworked it as an xfs-only ioctl.
IOWs, the "privatize the FIEXCHANGE" series should fix all these
problems for Christoph.
--D
> >
> > _scratch_mkfs >> $seqres.full
> > _scratch_mount
> > diff --git a/tests/generic/727 b/tests/generic/727
> > index 2cda49ea..1f9eebc5 100755
> > --- a/tests/generic/727
> > +++ b/tests/generic/727
> > @@ -20,6 +20,7 @@ _begin_fstest auto fiexchange swapext quick
> > # Import common functions.
> > . ./common/filter
> > . ./common/attr
> > +. ./common/reflink
> >
> > # real QA test starts here
> >
> > @@ -31,6 +32,7 @@ _require_command "$SETCAP_PROG" setcap
> > _require_xfs_io_command swapext '-v vfs -a'
> > _require_xfs_io_command startupdate
> > _require_scratch
> > +_require_scratch_reflink
> > _require_attrs security
> >
> > _scratch_mkfs >> $seqres.full
> > --
> > 2.39.2
> >
> >
>
>
next prev parent reply other threads:[~2023-11-17 22:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-08 15:24 [PATCH] generic/726,727: add missing _require_scratch_reflink Christoph Hellwig
2023-11-17 14:51 ` Zorro Lang
2023-11-17 22:09 ` Darrick J. Wong [this message]
2023-11-19 13:18 ` Zorro Lang
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=20231117220945.GH36175@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
--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