public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Eric Sandeen <sandeen@sandeen.net>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic/071: require falloc -k
Date: Wed, 20 Jul 2016 12:52:17 +0800	[thread overview]
Message-ID: <20160720045217.GT27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <20160719083047.GA21083@lst.de>

On Tue, Jul 19, 2016 at 10:30:47AM +0200, Christoph Hellwig wrote:
> On Mon, Jul 18, 2016 at 11:49:57PM -0700, Eric Sandeen wrote:
> > Some tests actually do run xfs_io on a real file, but we probably
> > don't want to go that way.
> > 
> > The test for finding it in help output seems way too specific,
> > 
> > _require_xfs_io_command "pwrite" "-Z"
> > 
> > fails as well because it doesn't hit the specific format in
> > the grep.
> > 
> > What if we loosen up the test; is this too loose? (look for param
> > preceded by whitespace or square bracket)
> 
> Seems like it's not loose enough as it still tries to run the test
> on NFS.

For this NFSv4.2 case, I think we have to actually run "falloc -k" to
check whether the underlying fs supports (FALLOC_FL_KEEP_SIZE) or not.

Current check in _require_xfs_io_command only checks whether xfs_io
knows the given option, not the underlying fs. And in this NFSv4.2 case,
NFSv4.2 supports fallocate(2), and xfs_io falloc command knows "-k"
option, so test runs on NFS.

Thanks,
Eryu

  reply	other threads:[~2016-07-20  4:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-18  8:06 [PATCH] generic/071: require falloc -k Christoph Hellwig
2016-07-18  8:47 ` Eryu Guan
2016-07-19  4:17   ` Christoph Hellwig
2016-07-19  6:49     ` Eric Sandeen
2016-07-19  8:30       ` Christoph Hellwig
2016-07-20  4:52         ` Eryu Guan [this message]
2016-07-20  5:34           ` Eric Sandeen
2016-07-20 12:40             ` Eryu Guan
2016-07-20  4:38       ` 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=20160720045217.GT27776@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=sandeen@sandeen.net \
    /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