From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2025.05.11 onto master branch
Date: Sun, 25 May 2025 20:37:21 +0800 [thread overview]
Message-ID: <e47d71caecb53f97ec8fa381ef17ef87@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 5516 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
has just been updated to v2025.05.11 version.
Thanks,
Zorro
The new head of the master branch is commit:
e161fc34861a f2fs/012: test red heart lookup
New commits:
Anthony Iliopoulos (2):
[00fb5168666c] fstests/MAINTAINERS: update ocfs2 mailing list address
[1d47ece86061] generic/211: completely remove obsolete test and related code
Chao Yu (1):
[e161fc34861a] f2fs/012: test red heart lookup
Christoph Hellwig (19):
[93699c621e98] xfs: check for zoned-specific errors in _try_scratch_mkfs_xfs
[d4d28552829e] common: notrun in mkfs_dev for too small zoned file systems
[f74792247a9e] common: support internal RT device in _require_realtime
[363069162ae1] common: support internal RT devices in scratch_mkfs_sized
[eae2dd124fa1] common: generalize _filter_agno
[42e226139f70] fstests: add a new rw_hint helper
[9e3423e418f0] xfs: add a test for zoned block accounting after remount
[133c38c5bd67] xfs: add a zoned growfs test
[66f5b97a09fb] xfs: add test to check for block layer reordering
[ac4afb483f4e] xfs: add a test to check that data growfs fails with internal rt device
[ef9667213d57] xfs: add a test for write lifetime hints
[9675a9d44545] xfs: add a test for writeback after close
[30bef4920470] xfs: test zone stream separation for two direct writers
[7afb07edeb49] xfs: test zone stream separation for two buffered writers
[0a014baacc4c] xfs: test zoned ENOSPC behavior with multiple writers
[57e6890bbce2] xfs: test zoned GC file defragmentation for sequential writers
[c63fc5f066c1] xfs: test zoned GC file defragmentation for random writers
[d6c292e41cce] xfs: test that xfs_repair does not mess up the zone used counter
[414de1b79cd7] xfs: test that truncate does not spuriously return ENOSPC
Darrick J. Wong (2):
[e72c9219f977] fsstress: fix attr_set naming
[aa8e98e506f5] xfs/349: don't run on kernels that don't support scrub
Hans Holmberg (1):
[cd5640a93381] xfs: test that we can handle spurious zone wp advancements
Nirjhar Roy (IBM) (2):
[7446236447e5] common: Move exit related functions to a common/exit
[3738433813f5] check: Replace exit with _fatal and _exit in check
Code Diffstat:
.gitignore | 2 +-
MAINTAINERS | 2 +-
check | 54 ++++-----
common/config | 17 ---
common/exit | 39 +++++++
common/filestreams | 11 +-
common/preamble | 3 +
common/punch | 39 +++----
common/rc | 52 ++++-----
common/xfs | 15 +++
ltp/fsstress.c | 4 +-
src/Makefile | 3 +-
.../aio-free-ring-with-bogus-nr-pages.c | 72 ------------
src/rw_hint.c | 48 ++++++++
tests/f2fs/012 | 70 ++++++++++++
tests/f2fs/012.out | 2 +
tests/generic/211 | 20 ----
tests/generic/211.out | 2 -
tests/xfs/349 | 2 +-
tests/xfs/634 | 40 +++++++
tests/xfs/634.out | 6 +
tests/xfs/635 | 78 +++++++++++++
tests/xfs/635.out | 11 ++
tests/xfs/636 | 37 ++++++
tests/xfs/636.out | 5 +
tests/xfs/637 | 24 ++++
tests/xfs/637.out | 3 +
tests/xfs/638 | 90 +++++++++++++++
tests/xfs/638.out | 4 +
tests/xfs/639 | 41 +++++++
tests/xfs/639.out | 1 +
tests/xfs/640 | 65 +++++++++++
tests/xfs/640.out | 3 +
tests/xfs/641 | 65 +++++++++++
tests/xfs/641.out | 3 +
tests/xfs/642 | 85 ++++++++++++++
tests/xfs/642.out | 2 +
tests/xfs/643 | 119 ++++++++++++++++++++
tests/xfs/643.out | 5 +
tests/xfs/644 | 124 +++++++++++++++++++++
tests/xfs/644.out | 5 +
tests/xfs/645 | 32 ++++++
tests/xfs/645.out | 5 +
tests/xfs/646 | 37 ++++++
tests/xfs/646.out | 1 +
tests/xfs/647 | 71 ++++++++++++
tests/xfs/647.out | 2 +
47 files changed, 1206 insertions(+), 215 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-05-25 12:37 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=e47d71caecb53f97ec8fa381ef17ef87@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