FS/XFS testing framework
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: djwong@kernel.org, fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCH] xfs: remove the v2log group
Date: Fri, 17 Jul 2026 16:37:17 +0800	[thread overview]
Message-ID: <alnpAUM8YfxmHcMv@zlang-mailbox> (raw)
In-Reply-To: <20260618134528.237508-1-hch@lst.de>

On Thu, Jun 18, 2026 at 03:45:28PM +0200, Christoph Hellwig wrote:
> v2log have been the default for more than a decade.  Merge all xfs log
> tests into the log group instead of splitting them up (with a lot of
> overlap).
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---

Highly welcome the reorganization of the groups. As the number of test
cases in xfstests grows, a clearer and more effective group classification
will definitely be helpful.

Reviewed-by: Zorro Lang <zlang@kernel.org>

>  doc/group-names.txt | 1 -
>  tests/generic/054   | 2 +-
>  tests/generic/055   | 2 +-
>  tests/xfs/095       | 2 +-
>  tests/xfs/119       | 2 +-
>  tests/xfs/135       | 2 +-
>  tests/xfs/137       | 2 +-
>  7 files changed, 6 insertions(+), 7 deletions(-)
> 
> diff --git a/doc/group-names.txt b/doc/group-names.txt
> index 158f84d36d31..424e2c4a1ca6 100644
> --- a/doc/group-names.txt
> +++ b/doc/group-names.txt
> @@ -142,7 +142,6 @@ union			tests from the unionmount test suite
>  unlink			O_TMPFILE unlinked files
>  unreliable_in_parallel	randomly fail when run in parallel with other tests
>  unshare			fallocate FALLOC_FL_UNSHARE_RANGE
> -v2log			XFS v2 log format tests
>  verity			fsverity
>  volume			btrfs volume management
>  whiteout		overlayfs whiteout functionality
> diff --git a/tests/generic/054 b/tests/generic/054
> index 0649b25930c6..f6eb8975b32e 100755
> --- a/tests/generic/054
> +++ b/tests/generic/054
> @@ -9,7 +9,7 @@
>  # In another qa test we can do more e.g. use fsstress.
>  #
>  . ./common/preamble
> -_begin_fstest shutdown log v2log auto
> +_begin_fstest shutdown log auto
>  
>  # Import common functions.
>  . ./common/filter
> diff --git a/tests/generic/055 b/tests/generic/055
> index e57f95faf897..f87fd7fb1850 100755
> --- a/tests/generic/055
> +++ b/tests/generic/055
> @@ -9,7 +9,7 @@
>  # * also can interrupt metadata with godown
>  #
>  . ./common/preamble
> -_begin_fstest shutdown log v2log auto quota stress
> +_begin_fstest shutdown log auto quota stress
>  
>  # Import common functions.
>  . ./common/filter
> diff --git a/tests/xfs/095 b/tests/xfs/095
> index da0d2ae4bb57..ab2ccfc7361c 100755
> --- a/tests/xfs/095
> +++ b/tests/xfs/095
> @@ -7,7 +7,7 @@
>  # Test upgrading the XFS log to v2
>  #
>  . ./common/preamble
> -_begin_fstest log v2log auto
> +_begin_fstest log auto
>  
>  # Import common functions.
>  . ./common/filter
> diff --git a/tests/xfs/119 b/tests/xfs/119
> index 7c1cd6a50ce5..e44d5a996a96 100755
> --- a/tests/xfs/119
> +++ b/tests/xfs/119
> @@ -9,7 +9,7 @@
>  # This can hang when things aren't working
>  #
>  . ./common/preamble
> -_begin_fstest log v2log auto freeze
> +_begin_fstest log auto freeze
>  
>  # Override the default cleanup function.
>  _cleanup()
> diff --git a/tests/xfs/135 b/tests/xfs/135
> index ec0b54ab45c3..e8c490a0c13f 100755
> --- a/tests/xfs/135
> +++ b/tests/xfs/135
> @@ -9,7 +9,7 @@
>  # and verified with xfs_logprint.
>  #
>  . ./common/preamble
> -_begin_fstest auto logprint quick v2log
> +_begin_fstest auto logprint quick log
>  
>  # Import common functions.
>  . ./common/log
> diff --git a/tests/xfs/137 b/tests/xfs/137
> index d97942bf671a..20d46f439b8a 100755
> --- a/tests/xfs/137
> +++ b/tests/xfs/137
> @@ -12,7 +12,7 @@
>  # xfs_repair detect the problem.
>  #
>  . ./common/preamble
> -_begin_fstest auto metadata v2log
> +_begin_fstest auto metadata log
>  
>  # Import common functions.
>  
> -- 
> 2.53.0
> 

      parent reply	other threads:[~2026-07-17  8:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-18 13:45 [PATCH] xfs: remove the v2log group Christoph Hellwig
2026-07-01 10:36 ` Andrey Albershteyn
2026-07-17  8:37 ` Zorro Lang [this message]

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=alnpAUM8YfxmHcMv@zlang-mailbox \
    --to=zlang@kernel.org \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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