From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to ae8c30c34c51
Date: Mon, 16 Aug 2021 00:31:24 +0800 [thread overview]
Message-ID: <6119415f.1c69fb81.e068.670f@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2610 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 many btrfs related fixes included in this
update, they're mainly for btrfs zoned device support from Naohiro Aota, and
some compatability fixes from Anand Jain and Boris Burkov.
There're also two new tests and they should all pass on latest v5.14-rc4
kernel.
Thanks,
Eryu
The new head of the master branch is commit:
ae8c30c34c51 xfs: test regression in shrink when the new EOFS splits a sparse inode cluster
New commits:
Anand Jain (4):
[705b0e60bcb7] common/rc: debug add _scratch_mount_options to the _scratch_mount
[1f940e6e67f5] btrfs/220: discard=sync support older kernel
[52e6b70d4681] btrfs/220: nologreplay support older kernel
[389302e73e11] btrfs/220: clear_cache fix for older kernel
Boris Burkov (1):
[ca71bde9fd8b] btrfs/220: fix clear_cache and inode_cache option tests
Darrick J. Wong (2):
[96d4e404f188] generic: test xattr operations only
[ae8c30c34c51] xfs: test regression in shrink when the new EOFS splits a sparse inode cluster
Luis Chamberlain (1):
[d26e07ebb6a2] fstests: use udevadm settle after pvremove
Marcos Paulo de Souza (1):
[5f883ecb049c] btrfs/177: Handle the different fi resize output formats
Naohiro Aota (5):
[72699dc08b1d] common/rc: introduce minimal fs size check
[40360a4264d4] common/rc: fix blocksize detection for btrfs
[fc5dc62bdd5d] btrfs/057: use _scratch_mkfs_sized to set filesystem size
[9ca8d2ac5e02] btrfs: add minimal file system size check
[6b96c8995ea2] shared/032: add check for zoned block device
Code Diffstat:
README | 4 ++
common/rc | 19 ++++-
tests/btrfs/057 | 2 +-
tests/btrfs/141 | 1 +
tests/btrfs/142 | 1 +
tests/btrfs/143 | 1 +
tests/btrfs/150 | 1 +
tests/btrfs/151 | 1 +
tests/btrfs/156 | 1 +
tests/btrfs/157 | 1 +
tests/btrfs/158 | 1 +
tests/btrfs/175 | 1 +
tests/btrfs/177 | 31 +++++++-
tests/btrfs/177.out | 4 +-
tests/btrfs/220 | 65 +++++++++++++----
tests/generic/081 | 5 +-
tests/generic/108 | 1 +
tests/generic/459 | 1 +
tests/generic/642 | 57 +++++++++++++++
tests/generic/642.out | 2 +
tests/shared/032 | 2 +
tests/xfs/176 | 190 ++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/176.out | 2 +
23 files changed, 372 insertions(+), 22 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2021-08-15 16:31 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=6119415f.1c69fb81.e068.670f@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