From: Eryu Guan <eguan@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/071: require falloc -k
Date: Mon, 18 Jul 2016 16:47:14 +0800 [thread overview]
Message-ID: <20160718084714.GD27776@eguan.usersys.redhat.com> (raw)
In-Reply-To: <1468829204-24593-1-git-send-email-hch@lst.de>
On Mon, Jul 18, 2016 at 11:06:44AM +0300, Christoph Hellwig wrote:
> NFSv4.2 supports fallocate, but not the FALLOC_FL_KEEP_SIZE option.
> To avoid a spurious failure test for the correct command.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> tests/generic/071 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/generic/071 b/tests/generic/071
> index 65ed0c7..9d0d136 100755
> --- a/tests/generic/071
> +++ b/tests/generic/071
> @@ -46,7 +46,7 @@ trap "_cleanup; exit \$status" 0 1 2 3 15
> _supported_fs generic
> _supported_os Linux
> _require_scratch
> -_require_xfs_io_command "falloc"
> +_require_xfs_io_command "falloc" "-k"
This stops generic/071 from running no matter what filesystem it's
testing, this is because _require_xfs_io_command only checks whether
xfs_io knows the option (-k) by searching it in help message, not really
running it, i.e.
xfs_io -c "help falloc" | grep -q "^ -k --"
but "help falloc" doesn't follow the normal xfs_io command help format
# xfs_io -c "help falloc"
falloc [-c] [-k] [-p] off len -- allocates space associated with part of a file via fallocate
So the check always returns false, and test always _notrun, with the
additional "-k" switch.
Perhaps we should update _require_xfs_io_command to actually run the
command with the provided additional option?
Thanks,
Eryu
next prev parent reply other threads:[~2016-07-18 8:47 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 [this message]
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
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=20160718084714.GD27776@eguan.usersys.redhat.com \
--to=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=hch@lst.de \
/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