From: Ritesh Harjani <riteshh@linux.ibm.com>
To: fstests <fstests@vger.kernel.org>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org,
Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [PATCHv2 0/4] generic: Add some tests around journal replay/recoveryloop
Date: Tue, 15 Mar 2022 19:58:55 +0530 [thread overview]
Message-ID: <cover.1647342932.git.riteshh@linux.ibm.com> (raw)
Hello,
Sending v2 with tests/ext4/ converted to tests/generic/
(although I had not received any review comments on v1).
It seems all of the tests which I had sent in v1 are not ext4 specific anyways.
So in v2, I have made those into tests/generic/.
These are some of the tests which when tested with ext4 fast_commit feature
w/o kernel fixes, could cause tests failures and/or KASAN bug (generic/486).
I gave these tests a run with default xfs, btrfs and f2fs configs (along with
ext4). No surprises observed.
[v1]: https://lore.kernel.org/all/cover.1644070604.git.riteshh@linux.ibm.com/
Ritesh Harjani (4):
generic/468: Add another falloc test entry
common/punch: Add block_size argument to _filter_fiemap_**
generic/676: Add a new shutdown recovery test
generic/677: Add a test to check unwritten extents tracking
common/punch | 12 +++++---
tests/generic/468 | 4 +++
tests/generic/468.out | 2 ++
tests/generic/676 | 72 +++++++++++++++++++++++++++++++++++++++++++
tests/generic/676.out | 7 +++++
tests/generic/677 | 64 ++++++++++++++++++++++++++++++++++++++
tests/generic/677.out | 6 ++++
7 files changed, 162 insertions(+), 5 deletions(-)
create mode 100755 tests/generic/676
create mode 100644 tests/generic/676.out
create mode 100755 tests/generic/677
create mode 100644 tests/generic/677.out
--
2.31.1
next reply other threads:[~2022-03-15 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 14:28 Ritesh Harjani [this message]
2022-03-15 14:28 ` [PATCHv2 1/4] generic/468: Add another falloc test entry Ritesh Harjani
2022-03-15 16:51 ` Darrick J. Wong
2022-03-29 10:59 ` Ritesh Harjani
2022-03-15 14:28 ` [PATCHv2 2/4] common/punch: Add block_size argument to _filter_fiemap_** Ritesh Harjani
2022-03-15 14:28 ` [PATCHv2 3/4] generic/676: Add a new shutdown recovery test Ritesh Harjani
2022-03-15 16:55 ` Darrick J. Wong
2022-03-29 11:32 ` Ritesh Harjani
2022-03-31 9:49 ` Ritesh Harjani
2022-03-15 14:28 ` [PATCHv2 4/4] generic/677: Add a test to check unwritten extents tracking Ritesh Harjani
2022-03-15 16:56 ` Darrick J. Wong
2022-03-29 11:34 ` Ritesh Harjani
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=cover.1647342932.git.riteshh@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).