From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to v2025.09.07
Date: Sun, 05 Oct 2025 23:56:48 +0800 [thread overview]
Message-ID: <0d2ac875ecb5396e52f1c180d48122f8@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2603 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.09.07 version.
Thanks,
Zorro
The new head of the master branch is commit:
911e9f168004 fstests: generic/733: avoid output difference due to bash's version
New commits:
Boris Burkov (1):
[cf73c0adc635] btrfs/301: test nested squota teardown
Christoph Hellwig (3):
[86a1a51cf62e] dmthin: _notrun when dm-thin setup fails
[aff1e92c3f47] generic/081: don't hang when running on devices with protection information
[fa19801cda23] generic/450: don't hang when running on devices with protection information
Filipe Manana (2):
[6dca84887d87] generic/363: mention btrfs kernel fix for block size < page size scenario
[bfa369f55a2b] fstests: add commit IDs for kernel fixes already merged upstream
Johannes Thumshirn (1):
[9d618786c0d1] btrfs/237: skip test on devices with conventional zones
Nirjhar Roy (IBM) (4):
[579a65fc0de0] btrfs/301: Make the test compatible with all the supported block sizes
[d6506d38a3ee] generic/274: Make the pwrite block sizes and offsets to 64k
[6ec632659993] btrfs/137: Make this test compatible with all supported block sizes
[f5822b2bced6] generic/563: Increase the iosize to cover for btrfs higher node sizes
Ojaswin Mujoo (1):
[8735e3e15fc7] generic/365: Fix false failure when mapping ends with free space
Qu Wenruo (3):
[6ca32795a99e] fstests: btrfs: add a new test case to verify compressed read
[8dd133d0763b] fstests: generic/228: do not rely on the bash core dump output
[911e9f168004] fstests: generic/733: avoid output difference due to bash's version
Code Diffstat:
common/dmthin | 10 ++++----
tests/btrfs/137 | 11 +++++----
tests/btrfs/137.out | 66 +++++++++++++++++++++++++--------------------------
tests/btrfs/237 | 9 +++++--
tests/btrfs/301 | 13 ++++++++--
tests/btrfs/337 | 53 +++++++++++++++++++++++++++++++++++++++++
tests/btrfs/337.out | 23 ++++++++++++++++++
tests/generic/081 | 3 ++-
tests/generic/211 | 2 +-
tests/generic/228 | 28 ++++++----------------
tests/generic/228.out | 2 +-
tests/generic/274 | 8 +++----
tests/generic/363 | 8 +++++--
tests/generic/365 | 6 +++++
tests/generic/459 | 6 +++--
tests/generic/563 | 2 +-
tests/generic/733 | 17 +++++++++++--
tests/generic/733.out | 1 -
tests/generic/771 | 2 +-
19 files changed, 186 insertions(+), 84 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-10-05 15:56 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=0d2ac875ecb5396e52f1c180d48122f8@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.