From: "Theodore Ts'o" <tytso@mit.edu>
To: Leah Rumancik <leah.rumancik@gmail.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] ext4/048: skip test of filename wipe if journal checkpoint is not supported
Date: Tue, 22 Jun 2021 22:02:24 -0400 [thread overview]
Message-ID: <YNKWMO0dY0hrMhqb@mit.edu> (raw)
In-Reply-To: <YNIphT6xiluxLrOm@google.com>
On Tue, Jun 22, 2021 at 11:18:45AM -0700, Leah Rumancik wrote:
> > diff --git a/tests/ext4/048 b/tests/ext4/048
> > index 51189618..35e6aa7f 100755
> > --- a/tests/ext4/048
> > +++ b/tests/ext4/048
> > @@ -93,6 +93,14 @@ _scratch_mkfs_sized $((128 * 1024 * 1024)) >> $seqres.full 2>&1
> > # create scratch dir for testing
> > # create some files with no name a substr of another name so we can grep later
> > _scratch_mount >> $seqres.full 2>&1
> > +
> > +# Use the presence of the journal checkpoint ioctl as a proxy of filename
> > +# wipe being supported
> > +if test -x $here/src/checkpoint_journal && \
> > + ! $here/src/checkpoint_journal $SCRATCH_MNT --dry-run ; then
> > + _notrun "filename wipe not supported"
> > +fi
>
> What if checkpoint_journal is not there? Should the test be
> skipped in that case as well?
I went back and forth on that one. In actual practice
checkpoint_journal should always be built in a valid xfstests
installation, so the case of it not existing should rarely if ever
arise. We don't actually _need_ checkpoint_journal to run the test;
we're just using it as a hint as to whether the filename wipe feature
is present. So I decided to let the test run if we couldn't find it,
on the theory that in the long run, all future kernels will have the
feature. But the case could be made in other direction....
- Ted
next prev parent reply other threads:[~2021-06-23 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 16:48 [PATCH] ext4/048: skip test of filename wipe if journal checkpoint is not supported Theodore Ts'o
2021-06-22 1:58 ` xuyang2018.jy
2021-06-23 2:42 ` xuyang2018.jy
2021-06-22 18:18 ` Leah Rumancik
2021-06-23 2:02 ` Theodore Ts'o [this message]
2021-06-23 20:58 ` Leah Rumancik
2021-06-23 21:00 ` Leah Rumancik
2021-06-23 21:31 ` Leah Rumancik
2021-07-04 10:47 ` Eryu Guan
2021-07-04 22:05 ` Theodore Ts'o
2021-07-05 7:56 ` 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=YNKWMO0dY0hrMhqb@mit.edu \
--to=tytso@mit.edu \
--cc=fstests@vger.kernel.org \
--cc=leah.rumancik@gmail.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