From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: for-next branch updated to 16ddbd1aee29
Date: Sun, 07 Aug 2022 23:51:08 +0800 [thread overview]
Message-ID: <20220807155112.E0989C433D6@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2499 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.07 release.
There're 4 new cases in this release (g/693, x/550, x/551 and x/552), but they
test for new features, so won't fail on old kernel generally. Those 3 xfs
cases are written for xfs' dax&reflink feature, it'll be in linux v5.20, if
no exception.
More details refer to below.
Thanks,
Zorro
The new head of the for-next branch is commit:
16ddbd1aee29 xfs: add memory failure test for partly-reflinked&dax file
New commits ([U]pdate, [N]ew):
Darrick J. Wong (4):
[U] [437f7742b8f1] xfs/432: fix this test when external devices are in use
[U] [bbfa39e7a5cf] xfs/291: convert open-coded _scratch_xfs_repair usage
[U] [b41bf16361fe] xfs/533: fix false negatives for this test
[U] [78a3ce021ba8] xfs/018: fix LARP testing for small block sizes
Nathan Huckleberry (2):
[U] [f57ffcf43811] fscrypt-crypt-util: add HCTR2 implementation
[N] [94e0bda55b36] generic: add tests for fscrypt policies with HCTR2
Shiyang Ruan (3):
[N] [2eaabb1d38cf] xfs: add memory failure test for dax mode
[N] [545d6b783773] xfs: add memory failure test for dax&reflink mode
[N] [16ddbd1aee29] xfs: add memory failure test for partly-reflinked&dax file
Zorro Lang (1):
[U] [378cf1c48143] fstests: add more dmerror related test cases into eio group
Code Diffstat:
.gitignore | 1 +
common/encrypt | 2 +
src/Makefile | 3 +-
src/fscrypt-crypt-util.c | 357 +++++++++++++++++++++++++++++++++-------
src/t_mmap_cow_memory_failure.c | 157 ++++++++++++++++++
tests/generic/484 | 2 +-
tests/generic/628 | 2 +-
tests/generic/629 | 2 +-
tests/generic/693 | 31 ++++
tests/generic/693.out | 16 ++
tests/xfs/018 | 15 +-
tests/xfs/018.out | 43 +----
tests/xfs/291 | 6 +-
tests/xfs/432 | 3 +-
tests/xfs/533 | 10 +-
tests/xfs/550 | 50 ++++++
tests/xfs/550.out | 9 +
tests/xfs/551 | 51 ++++++
tests/xfs/551.out | 9 +
tests/xfs/552 | 54 ++++++
tests/xfs/552.out | 9 +
21 files changed, 717 insertions(+), 115 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-08-07 15:51 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=20220807155112.E0989C433D6@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