From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2025.12.09
Date: Tue, 09 Dec 2025 22:31:16 +0800 [thread overview]
Message-ID: <c0629a4e66a1d5d80de5ff7c4739cec9@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2405 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.12.09 release.
Release Notes:
1) There're 5 new test cases in this release, include generic/784, generic/785,
generic/786, generic/787 and xfs/649.
2) The g/784, g/785 and x/649 are regression test cases to uncover known btrfs
or xfs bugs.
3) New "delegation" feature test coverage -- generic/786, generic/787.
4) New fsstress.c usage about option -f.
More updates and details refer to below, thanks for all these contributions.
Thanks,
Zorro
The new head of the for-next branch is commit:
df16c93a89d3 generic: add tests for file delegations
New commits:
Christoph Hellwig (2):
[37a5ef84413e] generic/484: force I/O to the data device for XFS
[74c8afa4f132] xfs/049: create the nested XFS file systems on the loop device
Darrick J. Wong (1):
[1b37d45c4373] fsstress: allow multiple suboptions to -f
Donald Douwsma (1):
[5760b2105985] xfs: test case for handling io errors when reading extended attributes
Filipe Manana (2):
[7e5537c5ec3f] generic: test a scenario of power failure after renames and fsyncs
[3970e305333e] generic: test journaling after renaming fsynced file and fsync parent dir
Jeff Layton (3):
[bf6ed3418e0f] common/rc: clean up after the _require_test_fcntl_setlease() test
[4e77fcc28c03] generic: add tests for directory delegations
[df16c93a89d3] generic: add tests for file delegations
Sidong Yang (1):
[d569940311fd] btrfs/339: test receive dump stream for different user
Code Diffstat:
common/locktest | 19 +-
common/rc | 11 +
common/scsi_debug | 8 +-
ltp/fsstress.c | 43 ++--
src/locktest.c | 621 +++++++++++++++++++++++++++++++++++++++++++++++++-
tests/btrfs/339 | 32 +++
tests/btrfs/339.out | 2 +
tests/generic/484 | 3 +
tests/generic/784 | 76 ++++++
tests/generic/784.out | 19 ++
tests/generic/785 | 73 ++++++
tests/generic/785.out | 4 +
tests/generic/786 | 19 ++
tests/generic/786.out | 2 +
tests/generic/787 | 20 ++
tests/generic/787.out | 2 +
tests/xfs/049 | 5 +-
tests/xfs/649 | 139 +++++++++++
tests/xfs/649.out | 2 +
19 files changed, 1068 insertions(+), 32 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-12-09 14:31 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=c0629a4e66a1d5d80de5ff7c4739cec9@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox