From: Ritesh Harjani <ritesh.list@gmail.com>
To: fstests <fstests@vger.kernel.org>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
"Darrick J . Wong" <djwong@kernel.org>,
Ritesh Harjani <ritesh.list@gmail.com>
Subject: [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop
Date: Thu, 31 Mar 2022 18:24:19 +0530 [thread overview]
Message-ID: <cover.1648730443.git.ritesh.list@gmail.com> (raw)
Hello,
The ext4 fast_commit kernel fix has landed into mainline tree [1].
In this v3, I have addressed review comments from Darrick.
Does this looks good to be picked up?
I have tested ext4 1k, 4k (w & w/o fast_commit). Also tested other FS with
default configs (like xfs, btrfs, f2fs). No surprises were seen.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bfdc502a4a4c058bf4cbb1df0c297761d528f54d
-ritesh
Changelogs:
===========
v2 => v3
=========
1. Addressed review comments from Darrick.
2. Rebased to latest master.
v1 => v2
=========
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/.
Summary
=========
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.
[v2]: https://lore.kernel.org/all/cover.1647342932.git.riteshh@linux.ibm.com/
[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/678: Add a new shutdown recovery test
generic/679: Add a test to check unwritten extents tracking
common/punch | 9 +++---
tests/generic/468 | 8 +++++
tests/generic/468.out | 2 ++
tests/generic/678 | 72 +++++++++++++++++++++++++++++++++++++++++++
tests/generic/678.out | 7 +++++
tests/generic/679 | 65 ++++++++++++++++++++++++++++++++++++++
tests/generic/679.out | 6 ++++
7 files changed, 165 insertions(+), 4 deletions(-)
create mode 100755 tests/generic/678
create mode 100644 tests/generic/678.out
create mode 100755 tests/generic/679
create mode 100644 tests/generic/679.out
--
2.31.1
next reply other threads:[~2022-03-31 12:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-31 12:54 Ritesh Harjani [this message]
2022-03-31 12:54 ` [PATCHv3 1/4] generic/468: Add another falloc test entry Ritesh Harjani
2022-04-03 23:28 ` Dave Chinner
2022-04-05 11:06 ` Ritesh Harjani
2022-04-05 22:00 ` Theodore Ts'o
2022-04-06 11:52 ` Ritesh Harjani
2022-04-06 4:05 ` Dave Chinner
2022-04-06 11:56 ` Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 2/4] common/punch: Add block_size argument to _filter_fiemap_** Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 3/4] generic/678: Add a new shutdown recovery test Ritesh Harjani
2022-04-03 23:38 ` Dave Chinner
2022-04-05 10:57 ` Ritesh Harjani
2022-03-31 12:54 ` [PATCHv3 4/4] generic/679: Add a test to check unwritten extents tracking Ritesh Harjani
2022-04-03 23:43 ` Dave Chinner
2022-04-05 10:56 ` Ritesh Harjani
2022-03-31 14:59 ` [PATCHv3 0/4] generic: Add some tests around journal replay/recoveryloop Zorro Lang
2022-03-31 16:19 ` Ritesh Harjani
2022-03-31 16:53 ` Ritesh Harjani
2022-04-01 5:30 ` Zorro Lang
2022-04-01 5:55 ` Ojaswin Mujoo
2022-04-01 17:04 ` Darrick J. Wong
2022-04-02 3:40 ` Zorro Lang
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.1648730443.git.ritesh.list@gmail.com \
--to=ritesh.list@gmail.com \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@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).