From: Eryu Guan <guaneryu@gmail.com>
To: fstests@vger.kernel.org
Subject: [ANNOUNCE] fstests: master branch updated to 0ad1c034838d
Date: Mon, 21 Dec 2020 00:55:57 +0800 [thread overview]
Message-ID: <5fdf8221.1c69fb81.8c656.9b9d@mx.google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2984 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. As usual, this update contains some new tests and
various bug fixes and improvements.
New btrfs tests btrfs/154 and btrfs/227 all currently fail with latest kernel.
And xfs/513 has been updated to catch a xfs bug, but it should pass with latest
kenrel.
Also, unionmount tests has been improved to run with custom overlay mount
options by assigning $OVERLAY_MOUNT_OPTIONS to UNIONMOUNT_MNTOPTIONS. You need
to update your local unionmount tests to latest to contain commit 95be14e
("Allow user provided options with or without -o")
Thanks,
Eryu
The new head of the master branch is commit:
0ad1c034838d overlay: run unionmount tests with custom overlay mount options
New commits:
Amir Goldstein (1):
[0ad1c034838d] overlay: run unionmount tests with custom overlay mount options
Brian Foster (1):
[62cf7ce77f4f] generic/563: use a loop device to avoid partition incompatibility
Eric Biggers (1):
[a225507009a3] generic: test for creating duplicate filenames in encrypted dir
Feiyu Zhu (1):
[0c5013c565b7] src/t_enospc.c: Fix an error for the loop initialization declaration
Filipe Manana (1):
[eabfcdfe9084] btrfs: test incremental send after removing a directory and all its files
Kaixu Xia (1):
[c2dd12732f31] xfs/513: fix the regression caused by mount option uqnoenforce
Nikolay Borisov (1):
[2a7406efecc2] btrfs: Update btrfs/215
Ritesh Harjani (1):
[72dc169b442e] generic: Add test to check for mounting a huge sparse dm device
Su Yue (1):
[a633d252e3c4] shared/032: add options for jffs2
Xiao Yang (1):
[90d76997831e] src/multi_open_unlink: Stop using attr_set
ethanwu (1):
[9f0744b16961] btrfs: test if rename handles dir item collision correctly
Code Diffstat:
common/overlay | 8 ++
common/rc | 31 ++++++++
src/Makefile | 2 +-
src/btrfs_crc32c_forged_name.py | 91 ++++++++++++++++++++++
src/multi_open_unlink.c | 8 +-
src/t_enospc.c | 8 +-
tests/btrfs/154 | 64 ++++++++++++++++
tests/btrfs/154.out | 2 +
tests/btrfs/215 | 14 ++--
tests/btrfs/227 | 122 +++++++++++++++++++++++++++++
tests/btrfs/227.out | 6 ++
tests/btrfs/group | 2 +
tests/generic/563 | 23 ++++--
tests/generic/620 | 62 +++++++++++++++
tests/generic/620.out | 3 +
tests/generic/621 | 166 ++++++++++++++++++++++++++++++++++++++++
tests/generic/621.out | 21 +++++
tests/generic/group | 2 +
tests/shared/032 | 5 ++
tests/xfs/513 | 4 +-
tests/xfs/513.out | 4 +-
21 files changed, 621 insertions(+), 27 deletions(-)
--
Eryu Guan
guaneryu@gmail.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-12-20 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-20 16:55 Eryu Guan [this message]
2020-12-21 1:02 ` [ANNOUNCE] fstests: master branch updated to 0ad1c034838d Xiao Yang
2020-12-21 3:07 ` Eryu Guan
2021-01-04 22:20 ` Darrick J. Wong
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=5fdf8221.1c69fb81.8c656.9b9d@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