From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2025.08.04
Date: Mon, 04 Aug 2025 01:05:03 +0800 [thread overview]
Message-ID: <fbf587151a610be1b48d11b892aaf7bf@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2507 bytes --]
Hi all,
The for-next branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
has just been updated and tagged as v2025.08.04 release.
Release Notes:
1) There's 1 new test case -- generic/771 in this release. It's a regression
test case for a known btrfs, and *might* cause crash on old btrfs.
2) New common helpers _require_inplace_writes (and _force_inplace_writes),
and _require_scratch_ext4_feature_enabled, welcome to use them properly.
I think they will be helpful for others.
More fixes on xfs, btrfs and ext4 parts, thanks for all these contributions!
Thanks,
Zorro
The new head of the for-next branch is commit:
3d57f543ae0c xfs/838: actually force usage of the realtime device
New commits:
Anthony Iliopoulos (1):
[9f6c59e0d485] xfs/189: fix remount barrier test failure
Boris Burkov (1):
[5dae2b3ca547] btrfs/301: enhance nested simple quotas test
Darrick J. Wong (6):
[aa14b84a8d1a] xfs/259: try to force loop device block size
[dca21d3724df] xfs/432: fix metadump loop device blocksize problems
[86950a4e23c1] generic/767: require fallocate support
[ca57558daefe] generic/767: only test the hardware atomic write unit
[8b81cf5ce725] generic/767: allow on any atomic writes filesystem
[3d57f543ae0c] xfs/838: actually force usage of the realtime device
Filipe Manana (2):
[57e68bd5c6bb] generic/211: verify if the filesystem being tested supports in place writes
[d8b702f89e01] generic: test fsync of file with 0 links and extents
Theodore Ts'o (1):
[c8434d36096d] ext4/028: require that the scratch file system has the extent feature enabled
Code Diffstat:
.gitignore | 1 +
common/atomicwrites | 6 +++
common/ext4 | 23 ++++++++---
common/metadump | 12 ++++--
common/rc | 108 ++++++++++++++++++++++++++++++++++++++++++++++++--
src/Makefile | 2 +-
src/unlink-fsync.c | 45 +++++++++++++++++++++
tests/btrfs/301 | 10 ++++-
tests/ext4/028 | 1 +
tests/generic/211 | 9 +----
tests/generic/563 | 2 +-
tests/generic/767 | 19 +++++++--
tests/generic/771 | 60 ++++++++++++++++++++++++++++
tests/generic/771.out | 4 ++
tests/xfs/078 | 4 +-
tests/xfs/189 | 2 +-
tests/xfs/259 | 2 +-
tests/xfs/613 | 3 +-
tests/xfs/838 | 1 +
19 files changed, 282 insertions(+), 32 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-08-03 17:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=fbf587151a610be1b48d11b892aaf7bf@kernel.org \
--to=zlang@kernel.org \
--cc=fstests@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 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.