From: "Darrick J. Wong" <djwong@kernel.org>
To: zlang@redhat.com
Cc: fstests@vger.kernel.org, linux-xfs@vger.kernel.org
Subject: Re: [PATCHSET 1/2] fstests: check new 6.15 behaviors
Date: Thu, 10 Jul 2025 09:16:10 -0700 [thread overview]
Message-ID: <20250710161610.GC2672039@frogsfrogsfrogs> (raw)
In-Reply-To: <174786719374.1398726.14706438540221180099.stgit@frogsfrogsfrogs>
On Wed, May 21, 2025 at 03:40:53PM -0700, Darrick J. Wong wrote:
> Hi all,
>
> Adjust fstests to check for new behaviors introduced in 6.15.
>
> If you're going to start using this code, I strongly recommend pulling
> from my git trees, which are linked below.
>
> With a bit of luck, this should all go splendidly.
> Comments and questions are, as always, welcome.
Hrm, can we get the first two patches into for-next, please?
I'll work on the last two and repost when they're ready.
--D
> --D
>
> fstests git tree:
> https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=linux-6.15-sync
> ---
> Commits in this patchset:
> * xfs/273: fix test for internal zoned filesystems
> * xfs/259: drop the 512-byte fsblock logic from this test
> * xfs/259: try to force loop device block size
> * xfs/432: fix metadump loop device blocksize problems
> ---
> common/metadump | 12 ++++++++++--
> common/rc | 29 +++++++++++++++++++++++++++++
> tests/generic/563 | 1 +
> tests/xfs/078 | 2 ++
> tests/xfs/259 | 25 +++++++++----------------
> tests/xfs/259.out | 7 -------
> tests/xfs/273 | 5 +++++
> tests/xfs/613 | 1 +
> 8 files changed, 57 insertions(+), 25 deletions(-)
>
>
next prev parent reply other threads:[~2025-07-10 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 22:40 [PATCHSET 1/2] fstests: check new 6.15 behaviors Darrick J. Wong
2025-05-21 22:41 ` [PATCH 1/4] xfs/273: fix test for internal zoned filesystems Darrick J. Wong
2025-05-23 5:17 ` Christoph Hellwig
2025-05-21 22:41 ` [PATCH 2/4] xfs/259: drop the 512-byte fsblock logic from this test Darrick J. Wong
2025-05-23 5:17 ` Christoph Hellwig
2025-05-21 22:41 ` [PATCH 3/4] xfs/259: try to force loop device block size Darrick J. Wong
2025-05-22 1:21 ` Dave Chinner
2025-05-28 22:36 ` Darrick J. Wong
2025-05-23 5:19 ` Christoph Hellwig
2025-05-28 22:22 ` Darrick J. Wong
2025-06-02 5:07 ` Christoph Hellwig
2025-06-03 14:36 ` Darrick J. Wong
2025-06-03 14:37 ` Christoph Hellwig
2025-05-21 22:41 ` [PATCH 4/4] xfs/432: fix metadump loop device blocksize problems Darrick J. Wong
2025-05-22 1:08 ` Dave Chinner
2025-05-28 22:37 ` Darrick J. Wong
2025-07-10 16:16 ` Darrick J. Wong [this message]
2025-07-10 18:26 ` [PATCHSET 1/2] fstests: check new 6.15 behaviors 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=20250710161610.GC2672039@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@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