From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to 0882b0913eae
Date: Sun, 12 Jun 2022 18:48:44 +0800 [thread overview]
Message-ID: <20220612104851.A35B7C34115@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2065 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.06.12 release.
This week we don't have many changes, but have 3 new test cases as xfs/081,
xfs/547 and xfs/548. The xfs/081 covers an old bug fix on linux v5.16, so
it won't break new kernel, but might cause testing hang on kernel without
this fix. The x/547 and x/548 cover a new xfs feature on later kernel 5.19
or 5.20, so they won't break your current test.
Thanks,
Zorro
The new head of the for-next branch is commit:
0882b0913eae xfs: Verify correctness of upgrading an fs to support large extent counters
New commits ([N]ew, [U]pdate):
Chandan Babu R (4):
[U] [5bb78c56ef59] xfs/270: Fix ro mount failure when nrext64 option is enabled
[U] [63b956a156ea] common/xfs: Add helper to check if nrext64 option is supported
[N] [9b448f06fe21] xfs: Verify that the correct inode extent counters are updated with/without nrext64
[N] [0882b0913eae] xfs: Verify correctness of upgrading an fs to support large extent counters
Naohiro Aota (1):
[U] [3493b8dc8b3d] btrfs/220: zoned: skip nodatacow mount option for zoned btrfs
Zorro Lang (2):
[U] [085faee2742c] xfs: corrupted xattr should not block removexattr
[N] [e937e23d2021] common/filter: filter out extra mount error output
Code Diffstat:
common/filter | 13 ++++++-
common/xfs | 12 ++++++
tests/btrfs/220 | 18 +++++----
tests/xfs/081 | 80 ++++++++++++++++++++++++++++++++++++++
tests/xfs/081.out | 2 +
tests/xfs/154 | 2 +-
tests/xfs/154.out | 2 +-
tests/xfs/158 | 2 +-
tests/xfs/158.out | 2 +-
tests/xfs/270 | 26 ++++++++++++-
tests/xfs/270.out | 1 -
tests/xfs/547 | 92 ++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/547.out | 13 +++++++
tests/xfs/548 | 112 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/548.out | 12 ++++++
15 files changed, 372 insertions(+), 17 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-06-12 10:48 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=20220612104851.A35B7C34115@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