public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to v2026.04.20
Date: Mon, 20 Apr 2026 00:49:32 +0800	[thread overview]
Message-ID: <bc0bc8bc447a8eb8dd0ef53c657e7906@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 4730 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 v2026.04.20 release.

Release Notes:
1) There're 5 new cases in this release.
2) g/792, g/793 and f2fs/024 provide coverage for known btrfs and f2fs
   regressions. x/668 and x/669 are new zoned related tests on XFS.
3) Fix and refactor atomic write test cases.

More ext4, xfs, btrfs, f2fs related fixes and updates refer to below, thanks
for all these contributions!

Thanks,
Zorro

The new head of the for-next branch is commit:

cac9fe2b8dc3 generic: test premature ENOSPC in zoned garbage collection

New commits:

Christoph Hellwig (1):
      [d59865ddf8e4] xfs: add a test for number of open zones on conventional devices

Darrick J. Wong (4):
      [04ee3a4f0d19] common: ignore stderr for the two new svcname helpers
      [78b8a11f8c2f] xfs/6{59-61}: force xfs_healer to run
      [c17136d0c6c4] xfs/805: adjust for new autofsck fsproperty defaults
      [dde983e4419a] xfs/841: actually compare the new filesystem contents to the proto dir

Disha Goel (1):
      [0bece2e05be1] generic/730: skip test if DAX mount option is enabled

Filipe Manana (2):
      [c34c06b9728c] fstests: add kernel commit IDs for patches already merged upstream
      [c4e03688706d] generic: test fsync against a removed directory

Hans Holmberg (2):
      [7a2fe2c2f7be] xfs/647: turn rt dev block device lookup into a common helper
      [8deafb5c487e] xfs: test that zone_gc_low_space writes start gc for rw fses

Jan Prusakowski (1):
      [56b35283cf8e] generic/050: handle f2fs as nojournal filesystem

Johannes Thumshirn (1):
      [cac9fe2b8dc3] generic: test premature ENOSPC in zoned garbage collection

Leo Martins (2):
      [a44a26f93b05] generic/301: skip extent count check on btrfs
      [2d614deaed29] btrfs: fix stale errno check in btrfs_encoded_read/write helpers

Long Li (1):
      [29dbf0703917] xfs/018: test log attr replay with zero-length attr value

Ojaswin Mujoo (6):
      [ea4d04e7b676] ext4/061,062: Minor fixes and refactoring
      [2c002c3a86c0] common/rc: Add _sysfs_queue_path helper with partition support
      [4dc8a079a670] generic/765: Fix sysfs queue path for nvme partitions
      [fb11f06d9026] generic/765: Ignore mkfs warning
      [53e68c2afbb9] generic/775: Fix an infinite loop due to variable name clash
      [f3e91c87aa9f] treewide: Use _sysfs_queue_path helper in all queue access locations

Yangyang Zang (2):
      [271d7a1257f7] common/config: export F2FS_RESIZE_PROG
      [39b31fe6e746] f2fs: add testcase to check resize corrupting root inode


Code Diffstat:

 common/config             |  1 +
 common/encrypt            |  7 ++---
 common/rc                 | 36 +++++++++++++++++++++---
 common/report             | 20 +++++++------
 common/xfs                | 30 +++++++++++++++++++-
 common/zoned              |  5 ++--
 src/btrfs_encoded_read.c  |  1 +
 src/btrfs_encoded_write.c |  1 +
 src/unlink-fsync.c        | 39 +++++++++++++++++++------
 tests/btrfs/076           | 11 +++++---
 tests/btrfs/237           |  5 ++--
 tests/btrfs/273           |  4 ++-
 tests/btrfs/283           |  4 ++-
 tests/btrfs/340           |  2 +-
 tests/btrfs/345           |  2 +-
 tests/btrfs/346           |  2 +-
 tests/btrfs/347           |  2 +-
 tests/ext4/061            | 28 ++++++++++++------
 tests/ext4/062            | 26 ++++++++++++-----
 tests/f2fs/024            | 39 +++++++++++++++++++++++++
 tests/f2fs/024.out        |  7 +++++
 tests/generic/050         | 12 ++++++++
 tests/generic/301         |  8 +++++-
 tests/generic/730         |  3 ++
 tests/generic/762         |  2 +-
 tests/generic/765         | 12 ++++----
 tests/generic/775         |  3 +-
 tests/generic/789         |  2 +-
 tests/generic/790         |  2 +-
 tests/generic/792         | 69 +++++++++++++++++++++++++++++++++++++++++++++
 tests/generic/792.out     | 10 +++++++
 tests/generic/793         | 53 ++++++++++++++++++++++++++++++++++
 tests/generic/793.out     |  2 ++
 tests/xfs/018             | 26 ++++++++++++++---
 tests/xfs/018.out         | 20 +++++++++++++
 tests/xfs/647             | 10 +------
 tests/xfs/659             |  3 ++
 tests/xfs/660             |  3 ++
 tests/xfs/661             |  4 +++
 tests/xfs/668             | 72 +++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/668.out         |  2 ++
 tests/xfs/669             | 68 ++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/669.out         |  1 +
 tests/xfs/805             |  7 +----
 tests/xfs/805.out         |  1 -
 tests/xfs/841             | 25 +++++++++++++++-
 46 files changed, 604 insertions(+), 88 deletions(-)
--
Zorro Lang
zlang@kernel.org

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

                 reply	other threads:[~2026-04-19 16:49 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=bc0bc8bc447a8eb8dd0ef53c657e7906@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