From: Zorro Lang <zlang@kernel.org>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: merge v2022.09.04 onto master branch
Date: Sun, 25 Sep 2022 20:10:45 +0800 [thread overview]
Message-ID: <20220925121048.5B0F8C433C1@smtp.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2471 bytes --]
Hi all,
The master branch of the xfstests repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
has just been updated to v2022.09.04 version (merged from for-next).
[TODO here]
Thanks,
Zorro
The new head of the master branch is commit:
890c50823b64 vfs: Add new setgid_create_acl test
New commits:
BingJing Chang (1):
[ea66d27cb5e6] fstests: btrfs: test incremental send for changed reference paths
Chandan Babu R (1):
[0044157d9027] xfs: Check if a direct write can result in a false ENOSPC error
Christoph Hellwig (2):
[aa309b96fb5d] btrfs/271: include common/fail_make_request
[3e8936c3e84d] btrfs/271: use the common fail_request setup helpers
Darrick J. Wong (3):
[f3c314574d01] common/xfs: fix _reset_xfs_sysfs_error_handling reset to actual defaults
[4f929ebc5928] common: disable infinite IO error retry for EIO shutdown tests
[de3717ae0985] common: filter internal errors during io error testing
Filipe Manana (1):
[e42fa9fec802] generic: test fsync after punching hole adjacent to an existing hole
Xiubo Li (1):
[c935c7dce550] ceph/004: fix the ceph.quota.max_bytes values
Yang Xu (3):
[f9bf0d5130e1] ext4/053: Remove nouser_xattr test
[c87543428673] vfs: Add new setgid_create_umask test
[890c50823b64] vfs: Add new setgid_create_acl test
Code Diffstat:
check | 1 +
common/dmerror | 4 +
common/fail_make_request | 1 +
common/rc | 50 +-
common/xfs | 38 +-
src/vfs/idmapped-mounts.c | 1207 +++++++++++++++++++++++++++++++++++++++++++++
src/vfs/idmapped-mounts.h | 2 +
src/vfs/utils.c | 14 +
src/vfs/utils.h | 1 +
src/vfs/vfstest.c | 558 ++++++++++++++++++++-
tests/btrfs/271 | 36 +-
tests/btrfs/271.out | 2 +
tests/btrfs/272 | 88 ++++
tests/btrfs/272.out | 3 +
tests/ceph/004 | 6 +-
tests/ext4/053 | 1 -
tests/generic/695 | 91 ++++
tests/generic/695.out | 15 +
tests/generic/696 | 46 ++
tests/generic/696.out | 2 +
tests/generic/697 | 33 ++
tests/generic/697.out | 2 +
tests/xfs/006.out | 6 +-
tests/xfs/264.out | 12 +-
tests/xfs/553 | 67 +++
tests/xfs/553.out | 9 +
26 files changed, 2248 insertions(+), 47 deletions(-)
--
Zorro Lang
zlang@kernel.org
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2022-09-25 12:10 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=20220925121048.5B0F8C433C1@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