From: Eryu Guan <guan@eryu.me>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: fstests@vger.kernel.org, linux-ext4@vger.kernel.org,
Theodore Ts'o <tytso@mit.edu>,
"Darrick J . Wong" <djwong@kernel.org>
Subject: Re: [PATCHv2 0/9] xfstests: 64K blocksize related fixes
Date: Mon, 2 Aug 2021 00:05:26 +0800 [thread overview]
Message-ID: <YQbGRrgd9d5y91WO@desktop> (raw)
In-Reply-To: <cover.1626844259.git.riteshh@linux.ibm.com>
On Wed, Jul 21, 2021 at 10:57:53AM +0530, Ritesh Harjani wrote:
> Hello,
>
> Below are the list of fixes mostly centered around 64K blocksize
> and with ext4 filesystem. Tested this with both 64K & 4K blocksize on Power
> with (ext4/ext3/ext2/xfs/btrfs).
>
> v1 -> v2
> 1. Address comments from Ted and Darrick mentioned at [1]
Thanks for the fixes! I've applied patch 1-4 and patch 8-9. Patch 5-7
may need more discusstions.
Thanks,
Eryu
>
> [1]: https://patchwork.kernel.org/cover/12318137
>
> 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
> common/rc: Add _mkfs_dev_blocksized functionality
> generic/620: Use _mkfs_dev_blocksized to use 4k bs
> common/attr: Cleanup end of line whitespaces issues
> common/attr: Reduce MAX_ATTRS to leave some overhead for 64K blocksize
>
> common/attr | 57 ++++++++++++++++++++++++++++++++++++-------
> common/rc | 47 +++++++++++++++++++++++++++++++++++
> tests/ext4/003 | 3 ++-
> tests/ext4/022 | 7 ++++--
> tests/ext4/027 | 4 +--
> tests/ext4/306 | 5 +++-
> tests/generic/031 | 14 +++++++----
> tests/generic/031.out | 16 ++++++------
> tests/generic/620 | 4 ++-
> 9 files changed, 128 insertions(+), 29 deletions(-)
>
> --
> 2.31.1
prev parent reply other threads:[~2021-08-01 16:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 5:27 [PATCHv2 0/9] xfstests: 64K blocksize related fixes Ritesh Harjani
2021-07-21 5:27 ` [PATCHv2 1/9] ext4/003: Fix this test on 64K platform for dax config Ritesh Harjani
2021-07-21 5:27 ` [PATCHv2 2/9] ext4/027: Correct the right code of block and inode bitmap Ritesh Harjani
2021-07-21 5:27 ` [PATCHv2 3/9] ext4/306: Add -b blocksize parameter too to avoid failure with DAX config Ritesh Harjani
2021-07-21 5:27 ` [PATCHv2 4/9] ext4/022: exclude this test for dax config on 64KB pagesize platform Ritesh Harjani
2021-07-21 5:27 ` [PATCHv2 5/9] generic/031: Fix the test case for 64k blocksize config Ritesh Harjani
2021-08-01 16:00 ` Eryu Guan
2021-08-03 5:00 ` Ritesh Harjani
2021-08-08 12:36 ` Eryu Guan
2021-07-21 5:27 ` [PATCHv2 6/9] common/rc: Add _mkfs_dev_blocksized functionality Ritesh Harjani
2021-07-21 5:28 ` [PATCHv2 7/9] generic/620: Use _mkfs_dev_blocksized to use 4k bs Ritesh Harjani
2021-08-01 16:03 ` Eryu Guan
2021-08-03 5:06 ` Ritesh Harjani
2021-08-08 13:32 ` Eryu Guan
2021-07-21 5:28 ` [PATCHv2 8/9] common/attr: Cleanup end of line whitespaces issues Ritesh Harjani
2021-07-21 5:28 ` [PATCHv2 9/9] common/attr: Reduce MAX_ATTRS to leave some overhead for 64K blocksize Ritesh Harjani
2021-08-01 16:05 ` Eryu Guan [this message]
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=YQbGRrgd9d5y91WO@desktop \
--to=guan@eryu.me \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.