From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, guaneryu@gmail.com
Cc: xuyang2018.jy@fujitsu.com, Theodore Ts'o <tytso@mit.edu>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET 0/8] fstests: random fixes
Date: Tue, 11 Jan 2022 13:50:08 -0800 [thread overview]
Message-ID: <164193780808.3008286.598879710489501860.stgit@magnolia> (raw)
Hi all,
Here is a pile of random fstests fixes: a couple to fix xfs_scrub
unicode detection; one to fix xfs/220 so that it tests QUOTARM again;
the usual adjustments to fstests to accomodate behavior changes added to
5.17; a regression test for CVE-2021-4155; and cleanups to make fstests
less dependent on XFS_IOC_ALLOCSP/FREESP since those are going away for
5.17.
If you're going to start using this mess, you probably ought to just
pull from my git trees, which are linked below.
This is an extraordinary way to destroy everything. Enjoy!
Comments and questions are, as always, welcome.
--D
kernel git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfs-linux.git/log/?h=random-fixes
xfsprogs git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfsprogs-dev.git/log/?h=random-fixes
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=random-fixes
---
.gitignore | 1
common/rc | 19 ++++++---
common/xfs | 12 +++++
ltp/fsx.c | 110 +++++++++++++++++++++++++++++++++++++++++++++++++-
ltp/iogen.c | 32 ++++++++++----
src/Makefile | 2 -
src/alloc.c | 66 +++++++++++++++++++++++++-----
src/allocstale.c | 117 +++++++++++++++++++++++++++++++++++++++++++++++++++++
tests/xfs/130 | 6 ++-
tests/xfs/130.out | 1
tests/xfs/220 | 30 ++++++++++----
tests/xfs/308 | 5 --
tests/xfs/308.out | 2 -
tests/xfs/832 | 56 +++++++++++++++++++++++++
tests/xfs/832.out | 2 +
15 files changed, 418 insertions(+), 43 deletions(-)
create mode 100644 src/allocstale.c
create mode 100755 tests/xfs/832
create mode 100644 tests/xfs/832.out
next reply other threads:[~2022-01-11 21:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 21:50 Darrick J. Wong [this message]
2022-01-11 21:50 ` [PATCH 1/8] common/rc: fix _check_xfs_scrub_does_unicode on newer versions of libc-bin Darrick J. Wong
2022-01-11 21:50 ` [PATCH 2/8] common/rc: fix unicode checker detection in xfs_scrub Darrick J. Wong
2022-01-11 21:50 ` [PATCH 3/8] xfs/220: fix quotarm syscall test Darrick J. Wong
2022-01-12 1:14 ` xuyang2018.jy
2022-01-14 3:23 ` xuyang2018.jy
2022-01-14 17:08 ` Darrick J. Wong
2022-01-17 1:06 ` xuyang2018.jy
2022-01-11 21:50 ` [PATCH 4/8] xfs: test fixes for new 5.17 behaviors Darrick J. Wong
2022-01-11 21:50 ` [PATCH 5/8] xfs: regression test for allocsp handing out stale disk contents Darrick J. Wong
2022-01-16 7:12 ` Eryu Guan
2022-01-18 3:37 ` Zorro Lang
2022-01-18 18:09 ` Darrick J. Wong
2022-01-19 4:07 ` Zorro Lang
2022-01-19 4:52 ` Darrick J. Wong
2022-01-11 21:50 ` [PATCH 6/8] fsx: add support for XFS_IOC_ALLOCSP Darrick J. Wong
2022-01-11 21:50 ` [PATCH 7/8] iogen: upgrade to fallocate Darrick J. Wong
2022-01-16 7:01 ` Eryu Guan
2022-01-17 17:15 ` Darrick J. Wong
2022-01-11 21:50 ` [PATCH 8/8] alloc: " Darrick J. Wong
2022-01-16 7:16 ` [PATCHSET 0/8] fstests: random fixes Eryu Guan
-- strict thread matches above, loose matches on Subject: below --
2021-07-07 0:21 Darrick J. Wong
2021-07-18 14:35 ` Eryu Guan
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=164193780808.3008286.598879710489501860.stgit@magnolia \
--to=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=guaneryu@gmail.com \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=xuyang2018.jy@fujitsu.com \
/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;
as well as URLs for NNTP newsgroup(s).