From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to b91889d79e1d
Date: Sun, 31 Jul 2022 22:40:25 +0800 [thread overview]
Message-ID: <20220731144028.750E8C433D6@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2821 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.07.31 release.
Release Notes:
1) There're 5 new cases this week -- btrfs/261, ext4/058, ext4/059, xfs/533 and
xfs/549, where both ext4 new cases will trigger kernel BUG/crash on linux
version < 5.19-rc3, then break fstests running, so remind that for downstream
kernel testing.
2) This release fixes a small regression issue on nfs, which was brought in last
week. More details refer to commit b91889d79e1d. So I'd like *not* to update
master branch (to v2022.07.24) this week, to avoid this regression (and other
secondary cause:). If everything goes well next week, I'll update it as usual.
More details see below.
Thanks,
Zorro
The new head of the for-next branch is commit:
b91889d79e1d seek_sanity_test: use XFS ioctls to determine file allocation unit size
New commits:
Darrick J. Wong (3):
[U] [50f6d4641036] dmlogwrites: skip generic tests when external logdev in use
[U] [91f2a0f472e6] common/rc: wait for udev before creating dm targets
[U] [b91889d79e1d] seek_sanity_test: use XFS ioctls to determine file allocation unit size
Naohiro Aota (1):
[U] [2925f3b7f773] btrfs/253: skip on zoned mode as we cannot change the chunk size
Qu Wenruo (1):
[N] [9347bb488cde] btrfs: add test case to make sure btrfs can handle one corrupted device
Sun Ke (2):
[N] [88ac8622fae1] ext4: set 256 blocks in a block group then apply io pressure
[N] [affcc6dd6735] ext4: resize an ext4 which resize_inode feature is disabled but has reserved GDT blocks.
Yang Xu (4):
[U] [196721f3b730] xfs/270: Fix syntax error
[N] [b994a3bc4395] xfs: test xfs_db whether still can get corrupted field value
[N] [b7962b76ec24] xfs: test mkfs.xfs whether terminate getsubopt arrays properly
[U] [8a74eaaebe2a] xfs/191: Add missing xfsprogs commit
Code Diffstat:
common/rc | 13 ++++++++
src/seek_sanity_test.c | 36 +++++++++++++++------
tests/btrfs/253 | 2 ++
tests/btrfs/261 | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/btrfs/261.out | 2 ++
tests/ext4/058 | 33 +++++++++++++++++++
tests/ext4/058.out | 2 ++
tests/ext4/059 | 41 ++++++++++++++++++++++++
tests/ext4/059.out | 2 ++
tests/generic/455 | 1 +
tests/generic/457 | 1 +
tests/generic/470 | 1 +
tests/generic/482 | 1 +
tests/xfs/191 | 7 ++--
tests/xfs/270 | 6 ++--
tests/xfs/533 | 34 ++++++++++++++++++++
tests/xfs/533.out | 5 +++
tests/xfs/549 | 29 +++++++++++++++++
tests/xfs/549.out | 2 ++
19 files changed, 292 insertions(+), 13 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-07-31 14:40 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=20220731144028.750E8C433D6@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 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.