From: Ritesh Harjani <riteshh@linux.ibm.com>
To: fstests@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Ritesh Harjani <riteshh@linux.ibm.com>
Subject: [PATCH 0/9] 64K blocksize related fixes
Date: Mon, 14 Jun 2021 11:58:04 +0530 [thread overview]
Message-ID: <cover.1623651783.git.riteshh@linux.ibm.com> (raw)
Below are the list of fixes mostly centered around 64K blocksize (on PPC64)
and with ext4 filesystem. Tested this with both 64K & 4K blocksize on Power
with (ext4/ext3/ext2/xfs/btrfs).
Ritesh Harjani (9):
ext4/003: Fix this test on 64K platform for dax config
ext4/027: Correct the right code of block and inode bitmap
ext4/306: Add -b blocksize parameter too to avoid failure with DAX config
ext4/022: exclude this test for dax config on 64KB pagesize platform
generic/031: Fix the test case for 64k blocksize config
gitignore: Add 031.out file to .gitignore
generic/620: Remove -b blocksize option for ext4
common/attr: Cleanup end of line whitespaces issues
common/attr: Reduce MAX_ATTRS to leave some overhead for 64K blocksize
.gitignore | 1 +
common/attr | 20 ++++++------
tests/ext4/003 | 3 +-
tests/ext4/022 | 7 ++--
tests/ext4/027 | 4 +--
tests/ext4/306 | 5 ++-
tests/generic/031 | 37 ++++++++++++++++++----
tests/generic/031.out.64k | 19 +++++++++++
tests/generic/{031.out => 031.out.default} | 0
tests/generic/620 | 7 ++++
10 files changed, 80 insertions(+), 23 deletions(-)
create mode 100644 tests/generic/031.out.64k
rename tests/generic/{031.out => 031.out.default} (100%)
--
2.31.1
next reply other threads:[~2021-06-14 6:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 6:28 Ritesh Harjani [this message]
2021-06-14 6:28 ` [PATCH 1/9] ext4/003: Fix this test on 64K platform for dax config Ritesh Harjani
2021-06-30 16:27 ` Theodore Ts'o
2021-07-08 6:24 ` Ritesh Harjani
2021-07-08 12:51 ` Theodore Ts'o
2021-06-14 6:28 ` [PATCH 2/9] ext4/027: Correct the right code of block and inode bitmap Ritesh Harjani
2021-06-14 16:40 ` Darrick J. Wong
2021-06-14 6:28 ` [PATCH 3/9] ext4/306: Add -b blocksize parameter too to avoid failure with DAX config Ritesh Harjani
2021-06-30 16:29 ` Theodore Ts'o
2021-06-14 6:28 ` [PATCH 4/9] ext4/022: exclude this test for dax config on 64KB pagesize platform Ritesh Harjani
2021-06-30 16:36 ` Theodore Ts'o
2021-06-14 6:28 ` [PATCH 5/9] generic/031: Fix the test case for 64k blocksize config Ritesh Harjani
2021-06-30 15:50 ` Darrick J. Wong
2021-06-30 17:18 ` Theodore Ts'o
2021-07-08 9:49 ` Ritesh Harjani
2021-06-14 6:28 ` [PATCH 6/9] gitignore: Add 031.out file to .gitignore Ritesh Harjani
2021-06-30 16:36 ` Theodore Ts'o
2021-06-14 6:28 ` [PATCH 7/9] generic/620: Remove -b blocksize option for ext4 Ritesh Harjani
2021-06-30 17:07 ` Theodore Ts'o
2021-07-08 10:01 ` Ritesh Harjani
2021-06-14 6:28 ` [PATCH 8/9] common/attr: Cleanup end of line whitespaces issues Ritesh Harjani
2021-06-30 15:50 ` Darrick J. Wong
2021-06-30 17:19 ` Theodore Ts'o
2021-06-14 6:28 ` [PATCH 9/9] common/attr: Reduce MAX_ATTRS to leave some overhead for 64K blocksize Ritesh Harjani
2021-06-30 15:51 ` Darrick J. Wong
2021-06-30 19:20 ` Theodore Ts'o
2021-07-09 5:12 ` Ritesh Harjani
2021-06-30 13:30 ` [PATCH 0/9] 64K blocksize related fixes 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.1623651783.git.riteshh@linux.ibm.com \
--to=riteshh@linux.ibm.com \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@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).