From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2025.02.16
Date: Sun, 16 Feb 2025 19:18:10 +0800 [thread overview]
Message-ID: <e94779b0b9fc94bb58847742aeebde0a@kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3429 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.02.16 release.
Release Notes:
1) There's 1 new test case -- generic/761 to cover a btrfs known issue.
2) Fix many test bugs/failures on btrfs, xfs and fscrypt.
More details refer to below, thanks for all these contributions!
Thanks,
Zorro
The new head of the for-next branch is commit:
c41a7602d1eb btrfs: skip tests that exercise compression property when using nodatasum
New commits:
Christoph Hellwig (2):
[47a2cc4e81ec] common: fix a spelling error in _require_zoned_device
[27266caa0927] xfs/614: remove the _require_loop call
Eric Biggers (1):
[a18fe0c141b0] fscrypt-crypt-util: fix KDF contexts for SM8650
Filipe Manana (9):
[163a3e23ad0e] generic: suggest fs specific fix only if the tested filesystem matches
[595c8433603d] btrfs: skip tests incompatible with compression when compression is enabled
[2bc083d85e38] btrfs/290: skip test if we are running with nodatacow mount option
[7d83ccfe3ef3] common/btrfs: add a _require_btrfs_no_nodatasum helper
[e0ece7b8f497] btrfs/333: skip the test when running with nodatacow or nodatasum
[d449f1724e93] btrfs/205: skip test when running with nodatasum mount option
[0bdc1e525b3a] btrfs: skip tests exercising data corruption and repair when using nodatasum
[4e822b538981] btrfs/281: skip test when running with nodatasum mount option
[c41a7602d1eb] btrfs: skip tests that exercise compression property when using nodatasum
Qu Wenruo (2):
[7e92cb991b0b] fstests: btrfs/226: use nodatasum mount option to prevent false alerts
[17fb49493426] fstests: add a generic test to verify direct IO writes with buffer contents change
Code Diffstat:
.gitignore | 1 +
common/btrfs | 7 +++
common/rc | 2 +-
src/Makefile | 3 +-
src/dio-writeback-race.c | 148 +++++++++++++++++++++++++++++++++++++++++++++++
src/fscrypt-crypt-util.c | 4 +-
tests/btrfs/048 | 3 +
tests/btrfs/059 | 3 +
tests/btrfs/140 | 4 +-
tests/btrfs/141 | 4 +-
tests/btrfs/157 | 4 +-
tests/btrfs/158 | 4 +-
tests/btrfs/205 | 5 ++
tests/btrfs/215 | 8 ++-
tests/btrfs/226 | 7 ++-
tests/btrfs/265 | 7 ++-
tests/btrfs/266 | 7 ++-
tests/btrfs/267 | 7 ++-
tests/btrfs/268 | 7 ++-
tests/btrfs/269 | 7 ++-
tests/btrfs/281 | 2 +
tests/btrfs/289 | 8 ++-
tests/btrfs/290 | 12 ++++
tests/btrfs/297 | 4 ++
tests/btrfs/333 | 5 ++
tests/generic/365 | 10 ++--
tests/generic/366 | 2 +-
tests/generic/367 | 2 +-
tests/generic/623 | 2 +-
tests/generic/631 | 2 +-
tests/generic/646 | 2 +-
tests/generic/649 | 2 +-
tests/generic/695 | 2 +-
tests/generic/700 | 4 +-
tests/generic/701 | 2 +-
tests/generic/702 | 2 +-
tests/generic/704 | 4 +-
tests/generic/707 | 4 +-
tests/generic/761 | 41 +++++++++++++
tests/generic/761.out | 2 +
tests/xfs/614 | 1 -
41 files changed, 321 insertions(+), 36 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2025-02-16 11:18 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=e94779b0b9fc94bb58847742aeebde0a@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.