From: Lukas Czerner <lczerner@redhat.com>
To: Zorro Lang <zlang@redhat.com>
Cc: fstests@vger.kernel.org
Subject: Re: [PATCH] generic/499: stop fsx from probing insert range call
Date: Tue, 10 Jul 2018 14:24:15 +0200 [thread overview]
Message-ID: <20180710122415.m5ntnavstegc35oy@localhost.localdomain> (raw)
In-Reply-To: <20180710073305.23740-1-zlang@redhat.com>
On Tue, Jul 10, 2018 at 03:33:05PM +0800, Zorro Lang wrote:
> On some old kernel which supports COLLAPSE_RANGE and ZERO_RANGE,
> but doesn't support INSERT_RANGE, this case alway fails as:
>
> QA output created by 499
> +main: filesystem does not support fallocate mode FALLOC_FL_INSERT_RANGE, disabling!
> Silence is golden
>
> fsx print one more line to break the golden image.
>
> Due to this case don't need to do INSERT_RANGE operations, so use
> -I options to prevent fsx from probing INSERT_RANGE call.
>
> Signed-off-by: Zorro Lang <zlang@redhat.com>
> ---
>
> Hi,
>
> 1) I think using -I option of fsx is better than _notrun when find the system
> doesn't support INSERT_RANGE.
>
> 2) Although PUCH_HOLE isn't needed either, when a system supports COLLAPSE_RANGE
> and ZERO_RANGE, it supports PUCH_HOLE too. So I don't use -H option.
Hi Zorro,
there is no real dependency between fallocate modes, so it is this way for
historical reasons and it might be different for different fs. Not that
this matters much.
>
> Thanks,
> Zorro
>
> tests/generic/499 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/generic/499 b/tests/generic/499
> index 99d6d308..a2eac6ab 100755
> --- a/tests/generic/499
> +++ b/tests/generic/499
> @@ -50,7 +50,7 @@ ENDL
>
> victim=$SCRATCH_MNT/a
> touch $victim
> -$here/ltp/fsx --replay-ops $tmp.fsxops $victim > $tmp.output || cat $tmp.output
> +$here/ltp/fsx -I --replay-ops $tmp.fsxops $victim > $tmp.output || cat $tmp.output
The test fails (while the others does not) because we tend to redirect
stderr as well, but we are not doing it here.
IMO the better fix would be to add 2>&1
-Lukas
>
> echo "Silence is golden"
> status=0
> --
> 2.14.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe fstests" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-10 12:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 7:33 [PATCH] generic/499: stop fsx from probing insert range call Zorro Lang
2018-07-10 12:24 ` Lukas Czerner [this message]
2018-07-10 12:38 ` 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=20180710122415.m5ntnavstegc35oy@localhost.localdomain \
--to=lczerner@redhat.com \
--cc=fstests@vger.kernel.org \
--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