fstests.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Amir Goldstein <amir73il@gmail.com>
To: Xiao Yang <yangx.jy@cn.fujitsu.com>
Cc: eguan@linux.alibaba.com, fstests <fstests@vger.kernel.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Theodore Tso <tytso@mit.edu>
Subject: Re: [PATCH v2 2/2] fsx: Add '-a' option to skip unsupported keep size automatically
Date: Mon, 6 Jan 2020 13:24:45 +0200	[thread overview]
Message-ID: <CAOQ4uxh91oRB03UGuqhSgASeY7-OtQD3wMRdOQ-SL0UBgdMPHQ@mail.gmail.com> (raw)
In-Reply-To: <20200106070654.13249-2-yangx.jy@cn.fujitsu.com>

On Mon, Jan 6, 2020 at 9:12 AM Xiao Yang <yangx.jy@cn.fujitsu.com> wrote:
>
> 1) Use '-a' option to skip unsupported keep size automatically even if
>    it's defined by --replay-ops.
> 2) Add $FSX_AVOID to tests which defines keep size by --replay-ops.
>
> Signed-off-by: Xiao Yang <yangx.jy@cn.fujitsu.com>
> ---
>  ltp/fsx.c         | 9 +++++++--
>  tests/generic/456 | 2 +-
>  tests/generic/469 | 2 +-
>  tests/generic/499 | 2 +-
>  tests/generic/511 | 2 +-
>  5 files changed, 11 insertions(+), 6 deletions(-)
>

A very strong NACK!

Why are you making this change?
Did you read the description of the tests and try to understand the sequence
prescribed in the replay-ops file?

Those are reproducers to specific issues that require a very specific sequence
of operations and it seems to me that 'keep_size' is there for a reason in every
one of those tests.

For example, take the test generic/456, which I wrote, it has this link in the
comment above fsxops to a very elaborate email from Ted explaining the
problem: https://marc.info/?l=linux-ext4&m=151137380830381&w=2

You cannot just remove 'keep_size' from the test because then the test
doesn't do what it is intended to do.

Did you read my reply to Eryu's patch which he referred you to?
https://spinics.net/lists/fstests/msg08007.html

Instead of allowing test generic/456 to run on fs which doesn't support
FL_KEEP_SIZE, you should change the test to *require* support for
FL_KEEP_SIZE as well as require support for punch/zero/collapse:

_require_xfs_io_command "falloc" "-k"
_require_xfs_io_command "fpunch"
_require_xfs_io_command "fzero"
_require_xfs_io_command "fcollapse"

Same for the other tests that you changed to ignore keep_size.

Thanks,
Amir.

  reply	other threads:[~2020-01-06 11:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-06  7:06 [PATCH v2 1/2] ltp/fsx.c: Add FALLOC_FL_KEEP_SIZE flag and '-K' option Xiao Yang
2020-01-06  7:06 ` [PATCH v2 2/2] fsx: Add '-a' option to skip unsupported keep size automatically Xiao Yang
2020-01-06 11:24   ` Amir Goldstein [this message]
2020-01-07  2:10     ` Xiao Yang
2020-01-07  6:47       ` Amir Goldstein
2020-01-07  7:44         ` Xiao Yang
2020-01-07  8:49           ` Amir Goldstein
2020-01-13  2:06             ` Xiao Yang

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=CAOQ4uxh91oRB03UGuqhSgASeY7-OtQD3wMRdOQ-SL0UBgdMPHQ@mail.gmail.com \
    --to=amir73il@gmail.com \
    --cc=darrick.wong@oracle.com \
    --cc=eguan@linux.alibaba.com \
    --cc=fstests@vger.kernel.org \
    --cc=tytso@mit.edu \
    --cc=yangx.jy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).