From: "Darrick J. Wong" <djwong@kernel.org>
To: djwong@kernel.org, zlang@redhat.com
Cc: Christoph Hellwig <hch@lst.de>,
Andrey Albershteyn <aalbersh@redhat.com>,
Zorro Lang <zlang@kernel.org>,
linux-xfs@vger.kernel.org, fstests@vger.kernel.org, guan@eryu.me
Subject: [PATCHSET] fstests: random fixes for v2024.01.14
Date: Tue, 06 Feb 2024 18:18:33 -0800 [thread overview]
Message-ID: <170727231361.3726171.14834727104549554832.stgit@frogsfrogsfrogs> (raw)
Hi all,
Here's the usual odd fixes for fstests. Most of these are cleanups and
bug fixes for the recently merged xfs metadump v2 testing code.
This second attempt fixes a severe bug in the cleanup code from the
refactored metadump testing code and adds a few adjustments that the
maintainer asked for.
If you're going to start using this code, I strongly recommend pulling
from my git trees, which are linked below.
This has been running on the djcloud for months with no problems. Enjoy!
Comments and questions are, as always, welcome.
--D
fstests git tree:
https://git.kernel.org/cgit/linux/kernel/git/djwong/xfstests-dev.git/log/?h=random-fixes-2024.01.14
---
Commits in this patchset:
* generic/256: constrain runtime with TIME_FACTOR
* common/xfs: simplify maximum metadump format detection
* common/populate: always metadump full metadata blocks
* xfs/336: fix omitted -a and -o in metadump call
* common: refactor metadump v1 and v2 tests, version 2
* xfs/{129,234,253,605}: disable metadump v1 testing with external devices
* xfs/503: test metadump obfuscation, not progressbars
* xfs/503: split copy and metadump into two tests
* common/xfs: only pass -l in _xfs_mdrestore for v2 metadumps
* xfs/122: fix for xfs_attr_shortform removal in 6.8
---
common/metadump | 152 +++++++++++++++++++++++++++++++++++++++++++++++++++++
common/populate | 2 -
common/rc | 10 ---
common/xfs | 49 ++++++++++++++++-
tests/generic/256 | 7 ++
tests/xfs/122.out | 2 +
tests/xfs/129 | 91 ++------------------------------
tests/xfs/234 | 92 ++------------------------------
tests/xfs/253 | 90 ++-----------------------------
tests/xfs/284 | 4 +
tests/xfs/291 | 32 ++++-------
tests/xfs/336 | 2 -
tests/xfs/432 | 31 ++---------
tests/xfs/503 | 82 ++++-------------------------
tests/xfs/503.out | 6 +-
tests/xfs/601 | 54 +++++++++++++++++++
tests/xfs/601.out | 4 +
tests/xfs/605 | 92 +-------------------------------
18 files changed, 318 insertions(+), 484 deletions(-)
create mode 100644 common/metadump
create mode 100755 tests/xfs/601
create mode 100755 tests/xfs/601.out
next reply other threads:[~2024-02-07 2:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 2:18 Darrick J. Wong [this message]
2024-02-07 2:18 ` [PATCH 01/10] generic/256: constrain runtime with TIME_FACTOR Darrick J. Wong
2024-02-07 2:18 ` [PATCH 02/10] common/xfs: simplify maximum metadump format detection Darrick J. Wong
2024-02-07 2:18 ` [PATCH 03/10] common/populate: always metadump full metadata blocks Darrick J. Wong
2024-02-07 2:18 ` [PATCH 04/10] xfs/336: fix omitted -a and -o in metadump call Darrick J. Wong
2024-02-07 2:19 ` [PATCH 05/10] common: refactor metadump v1 and v2 tests, version 2 Darrick J. Wong
2024-02-07 9:15 ` Zorro Lang
2024-02-07 2:19 ` [PATCH 06/10] xfs/{129,234,253,605}: disable metadump v1 testing with external devices Darrick J. Wong
2024-02-07 2:19 ` [PATCH 07/10] xfs/503: test metadump obfuscation, not progressbars Darrick J. Wong
2024-02-07 2:19 ` [PATCH 08/10] xfs/503: split copy and metadump into two tests Darrick J. Wong
2024-02-07 2:19 ` [PATCH 09/10] common/xfs: only pass -l in _xfs_mdrestore for v2 metadumps Darrick J. Wong
2024-02-07 2:19 ` [PATCH 10/10] xfs/122: fix for xfs_attr_shortform removal in 6.8 Darrick J. Wong
-- strict thread matches above, loose matches on Subject: below --
2024-01-25 19:04 [PATCHSET] fstests: random fixes for v2024.01.14 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=170727231361.3726171.14834727104549554832.stgit@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=guan@eryu.me \
--cc=hch@lst.de \
--cc=linux-xfs@vger.kernel.org \
--cc=zlang@kernel.org \
--cc=zlang@redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).