linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: fstests@vger.kernel.org,
	Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4/026: skip test if kernel does not support the ea_inode feature
Date: Mon, 9 Oct 2017 09:40:10 +1100	[thread overview]
Message-ID: <20171008224010.GY15067@dastard> (raw)
In-Reply-To: <20171008215110.qxhel7nkcsifybu2@thunk.org>

On Sun, Oct 08, 2017 at 05:51:10PM -0400, Theodore Ts'o wrote:
> On Mon, Oct 09, 2017 at 08:41:17AM +1100, Dave Chinner wrote:
> > On Sun, Oct 08, 2017 at 03:23:24PM -0400, Theodore Ts'o wrote:
> > > Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> > > ---
> > >  tests/ext4/026 | 3 ++-
> > >  1 file changed, 2 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/tests/ext4/026 b/tests/ext4/026
> > > index 94a737ce..ba77f36e 100755
> > > --- a/tests/ext4/026
> > > +++ b/tests/ext4/026
> > > @@ -53,7 +53,8 @@ _require_attrs
> > >  _require_ext4_mkfs_feature ea_inode
> > >  
> > >  _scratch_mkfs_ext4 -O ea_inode >/dev/null 2>&1
> > > -_scratch_mount
> > > +_scratch_mount >/dev/null 2>&1 \
> > > +	|| _notrun "kernel doesn't support ea_inode feature on $FSTYP"
> > 
> > Needs to be in a _requires check?
> 
> There's only one test currently testing ea_inode at the moment, but
> sure, I can make it into a _requires check.

I note there's a _require_ext4_mkfs_feature check above. Perhaps
just turn that into a _require_ext4_feature that checks both mkfs
and whether the kernel supports the functionality? That's typically
what we've done in the past - one _require rule to check all
aspects of support needed to use the feature...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2017-10-08 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-08 19:23 [PATCH] ext4/026: skip test if kernel does not support the ea_inode feature Theodore Ts'o
2017-10-08 21:41 ` Dave Chinner
2017-10-08 21:51   ` Theodore Ts'o
2017-10-08 22:40     ` Dave Chinner [this message]
2017-10-09  6:00       ` Amir Goldstein
2017-10-09  6:37         ` Eryu Guan

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=20171008224010.GY15067@dastard \
    --to=david@fromorbit.com \
    --cc=fstests@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).