All of lore.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 v2024.10.14
Date: Mon, 14 Oct 2024 00:53:27 +0800	[thread overview]
Message-ID: <a9295329d0ee7f8e0e64980ac4fc18ff@kernel.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2822 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 v2024.10.14 release.

Release Notes:
1) There's not new test case in this relase.
2) The fsstress.c supports FALLOC_FL_UNSHARE_RANGE after fsx supported it.
3) Fix some bugs in common/ and src/ .
4) Improve some btrfs, xfs and generic test cases.

More details refer to below, thanks for all these contributions.

Thanks,
Zorro

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

891f4995ab07 src/fiexchange.h: add the start-commit/commit-range ioctls

New commits:

An Long (2):
      [e0c84186bfda] src/Makefile: install two necessary files
      [37f61a8fd323] btrfs/315: update filter to match mount cmd

Chao Yu (1):
      [4c9c08ec05c6] src/min_dio_alignment: don't return invalid dio_offset_align

Christoph Hellwig (1):
      [74777e97c56b] generic/694: sync before sampling i_blocks

Daniel Gomez (1):
      [dd0eeae9ead0] common/config: fix RECREATE_TEST_DEV initialization

Darrick J. Wong (3):
      [cf838edbaec7] common/populate: fix bash syntax error in _fill_fs
      [ff07e0a32936] fsstress: add support for FALLOC_FL_UNSHARE_RANGE
      [891f4995ab07] src/fiexchange.h: add the start-commit/commit-range ioctls

Filipe Manana (2):
      [b37aa9c8b0f9] btrfs: update some tests to be able to run with btrfs-progs v6.11
      [8babf87596c8] btrfs/322: add git commit ID

Hans Holmberg (2):
      [0ffcda29e8a0] common: make rt_ops local in _try_scratch_mkfs_sized
      [2f7e1b8a6f09] xfs/157,xfs/547,xfs/548: switch to using _scratch_mkfs_sized

Mark Harmstone (2):
      [c9a2881aa6f8] common/fail_make_request: fix error message
      [f4b00fafa4ef] btrfs/318: add _require_loop

Qu Wenruo (1):
      [034e56559337] fstests: generic/563: use fs blocksize to do the writes


Code Diffstat:

 common/config            |  2 +-
 common/fail_make_request |  2 +-
 common/filter.btrfs      |  5 ++++-
 common/populate          |  2 +-
 common/rc                |  1 +
 ltp/fsstress.c           | 14 ++++++++++++++
 m4/package_xfslibs.m4    |  2 ++
 src/Makefile             |  2 +-
 src/fiexchange.h         | 26 ++++++++++++++++++++++++++
 src/global.h             |  4 ++++
 src/min_dio_alignment.c  |  2 +-
 tests/btrfs/006.out      |  2 --
 tests/btrfs/100.out      |  2 --
 tests/btrfs/101.out      |  2 --
 tests/btrfs/218.out      |  1 -
 tests/btrfs/254.out      |  1 -
 tests/btrfs/315          |  7 ++++++-
 tests/btrfs/318          |  1 +
 tests/btrfs/322          |  2 +-
 tests/generic/563        | 10 ++++++----
 tests/generic/694        |  4 ++++
 tests/xfs/157            | 12 ++++++++----
 tests/xfs/547            |  4 +++-
 tests/xfs/548            |  2 +-
 24 files changed, 86 insertions(+), 26 deletions(-)
--
Zorro Lang
zlang@kernel.org

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

                 reply	other threads:[~2024-10-13 16:53 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=a9295329d0ee7f8e0e64980ac4fc18ff@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.