From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to ea1962cc9eaa
Date: Sun, 29 Aug 2021 22:51:41 +0800 [thread overview]
Message-ID: <612b9f01.1c69fb81.5b6b6.e230@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2025 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
have just been updated. There're 4 new tests and 2 bug fixes. Two of the four
new tests fail on btrfs with v5.15-rc7 kernel:
- btrfs/246: the fix has been merged but not in Linus tree yet
- generic/647: test hangs on btrfs, looks like a bug in btrfs, you may want to
skip it for now in your automatic test runs
Thanks,
Eryu
The new head of the master branch is commit:
ea1962cc9eaa btrfs: make sure btrfs can create compressed inline extent
New commits:
Andreas Gruenbacher (1):
[d3cbdabffc4c] generic: Test page faults during read and write
Darrick J. Wong (1):
[90199d806150] idmap: override btrfs_ioctl_vol_args_v2 if system header doesn't have subvolid
Luis Chamberlain (1):
[0e4dd8b9d2c8] common/rc: fix ignoring of errors on
Murphy Zhou (1):
[bdaa90aae7fc] generic: check log recovery with readonly mount
Qu Wenruo (1):
[ea1962cc9eaa] btrfs: make sure btrfs can create compressed inline extent
Theodore Ts'o (1):
[f4660739fedd] ext4: add test to validate the large_dir feature
Code Diffstat:
.gitignore | 1 +
common/rc | 4 +-
configure.ac | 2 +-
src/Makefile | 2 +-
src/dirstress.c | 7 +-
src/idmapped-mounts/idmapped-mounts.c | 6 +-
src/mmap-rw-fault.c | 186 ++++++++++++++++++++++++++++++++++
tests/btrfs/246 | 49 +++++++++
tests/btrfs/246.out | 5 +
tests/ext4/052 | 71 +++++++++++++
tests/ext4/052.out | 2 +
tests/generic/646 | 42 ++++++++
tests/generic/646.out | 2 +
tests/generic/647 | 35 +++++++
tests/generic/647.out | 2 +
15 files changed, 410 insertions(+), 6 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-08-29 14: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=612b9f01.1c69fb81.5b6b6.e230@mx.google.com \
--to=guaneryu@gmail.com \
--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