From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to bf1ef26900ee
Date: Sun, 21 Aug 2022 23:23:15 +0800 [thread overview]
Message-ID: <20220821152318.9BABBC433D6@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2966 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 v2022.08.21 release.
Release note:
1. There're two new cases this release, btrfs/277 for a btrfs new feature,
generic/694 for a known issue of exfat fs. So both of them generally
won't break downstream linux testing.
2. A big change from Darrick on dmerror improve, help it support external log
and rt device, and help ext4 part support external logdev better, and move
ext4 specific helper into common/ext4 file (which is just created in this
release). Thanks Darrick, and inform ext4 folks.
Thanks for all your contribution, and more details see below.
Thanks,
Zorro
The new head of the for-next branch is commit:
bf1ef26900ee src/t_ofd_locks.c: Reset errno to zero
New commits ([N]ew, [U]pdate:
Boris Burkov (1):
[N] [192f5297b54f] fstests: add btrfs fs-verity send/recv test
Darrick J. Wong (7):
[U] [04307f499d13] xfs/{015,042,076}: fix mkfs failures with nrext64=1
[U] [67afd5c74246] common/rc: move ext4-specific helpers into a separate common/ext4 file
[U] [e88c0d38eeda] common/rc: move XFS-specific parts of _scratch_options into common/xfs
[U] [92caf7ebe14d] common/ext4: provide custom ext4 scratch fs options
[U] [acf0424671ff] dmerror: support external log and realtime devices
[U] [49272aacac85] common: refactor fail_make_request boilerplate
[U] [6049ccca12ab] fail_make_request: teach helpers about external devices
Pavel Reichl (1):
[N] [87d9aea81007] generic: test i_blocks for large files
Wang Yugui (1):
[U] [c9734480a1dd] fstests: add missing _require_scratch
Yang Xu (1):
[U] [bf1ef26900ee] src/t_ofd_locks.c: Reset errno to zero
Code Diffstat:
common/config | 4 +
common/dmerror | 163 +++++++++++++++++++++++++++++++++++++--
common/ext4 | 193 +++++++++++++++++++++++++++++++++++++++++++++++
common/fail_make_request | 63 ++++++++++++++++
common/rc | 193 ++++-------------------------------------------
common/xfs | 23 ++++++
src/t_ofd_locks.c | 2 +
tests/btrfs/088 | 14 ++--
tests/btrfs/150 | 13 ++--
tests/btrfs/202 | 1 +
tests/btrfs/215 | 1 +
tests/btrfs/268 | 1 +
tests/btrfs/269 | 1 +
tests/btrfs/270 | 1 +
tests/btrfs/277 | 115 ++++++++++++++++++++++++++++
tests/btrfs/277.out | 59 +++++++++++++++
tests/generic/019 | 40 ++--------
tests/generic/441 | 2 +-
tests/generic/487 | 2 +-
tests/generic/694 | 47 ++++++++++++
tests/generic/694.out | 2 +
tests/xfs/015 | 4 +-
tests/xfs/042 | 14 ++--
tests/xfs/042.out | 4 +-
tests/xfs/076 | 2 +-
25 files changed, 711 insertions(+), 253 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-08-21 15:23 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=20220821152318.9BABBC433D6@smtp.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