All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Zorro Lang <zlang@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>,
	"Darrick J . Wong " <djwong@kernel.org>,
	linux-xfs@vger.kernel.org, fstests@vger.kernel.org
Subject: Re: fix kernels without v5 support
Date: Mon, 8 Apr 2024 16:59:39 +0200	[thread overview]
Message-ID: <20240408145939.GA26949@lst.de> (raw)
In-Reply-To: <20240408145554.ezvbgolzjppua4in@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Mon, Apr 08, 2024 at 10:55:54PM +0800, Zorro Lang wrote:
> > this series ensures tests pass on kernels without v5 support.  As a side
> > effect it also removes support for historic kernels and xfsprogs without
> > any v5 support, and without mkfs input validation.
> 
> Thanks for doing this! I'm wondering if fstests should do this "removing"
> earlier than xfs? Hope to hear more opinions from xfs list and other fstests
> users (especially from some LTS distro) :)

What is being removed is support for kernels and xfsprogs that do not
support v5 file systems at all, not testing on v4 file system for the
test device and the large majority of tests using the scratch device
without specifying an explicit version.

The exception from the above are two sub-cases for v4 that are removed in
the this series - if we really care about them I could move them into
separate tests, but I doubt it's worth it.


  reply	other threads:[~2024-04-08 14:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-08 13:32 fix kernels without v5 support Christoph Hellwig
2024-04-08 13:32 ` [PATCH 1/6] xfs: remove support for tools and kernels with " Christoph Hellwig
2024-04-08 15:03   ` Eric Biggers
2024-04-08 15:04     ` Christoph Hellwig
2024-04-09 15:26   ` Darrick J. Wong
2024-04-29  9:34   ` Chandan Babu R
2024-04-29  9:53     ` Christoph Hellwig
2024-04-29 14:20     ` Zorro Lang
2024-04-08 13:32 ` [PATCH 2/6] remove xfs/096 Christoph Hellwig
2024-04-09 15:27   ` Darrick J. Wong
2024-04-08 13:32 ` [PATCH 3/6] xfs/078: remove the 512 byte block size sub-case Christoph Hellwig
2024-04-09 15:32   ` Darrick J. Wong
2024-04-08 13:32 ` [PATCH 4/6] xfs/263: remove the nocrc sub-test Christoph Hellwig
2024-04-09 15:57   ` Darrick J. Wong
2024-04-10  4:11     ` Christoph Hellwig
2024-04-08 13:32 ` [PATCH 5/6] xfs/522: use reflink instead of crc as test feature Christoph Hellwig
2024-04-09 15:39   ` Darrick J. Wong
2024-04-08 13:32 ` [PATCH 6/6] xfs: don't run tests that require v4 file systems when not supported Christoph Hellwig
2024-04-09 15:56   ` Darrick J. Wong
2024-04-10  4:14     ` Christoph Hellwig
2024-04-10 15:05       ` Darrick J. Wong
2024-04-08 14:55 ` fix kernels without v5 support Zorro Lang
2024-04-08 14:59   ` Christoph Hellwig [this message]
2024-04-08 19:00     ` Zorro Lang
2024-04-10 14:42       ` Zorro Lang
2024-04-10 14:51         ` Christoph Hellwig
2024-04-10 15:16           ` Darrick J. Wong
2024-04-10 15:18             ` Christoph Hellwig
2024-04-10 16:03               ` Darrick J. Wong
2024-04-10 19: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=20240408145939.GA26949@lst.de \
    --to=hch@lst.de \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=zlang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.