From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org,
ritesh.list@gmail.com, djwong@kernel.org, zlang@kernel.org,
fdmanana@kernel.org, quwenruo.btrfs@gmx.com
Subject: Re: [PATCH v3 0/4] btrfs: Misc test fixes for large block/node sizes
Date: Mon, 25 Aug 2025 11:38:15 +0530 [thread overview]
Message-ID: <0ab6b334-a0ba-4797-9aed-c941f9a0b614@gmail.com> (raw)
In-Reply-To: <aKv6tra6TKzX3x2l@li-dc0c254c-257c-11b2-a85c-98b6c1322444.ibm.com>
On 8/25/25 11:25, Ojaswin Mujoo wrote:
> On Wed, Aug 20, 2025 at 08:15:03AM +0000, Nirjhar Roy (IBM) wrote:
>> Some of the btrfs and generic tests are written with 4k block/node size in mind.
>> This patch fixes some of those tests to be compatible with other block/node sizes too.
>> We caught these bugs while running the auto group tests on btrfs with large
>> block/node sizes.
>>
>> [v2] -> v3
>> 1. Added RBs by Qu Wenruo in btrfs/{301, 137}
>> 2. Updated the commit message of generic/563 with a more detailed explanation
>> by Qu Wenrou.
>> 3. Reverted by block size from 64k to 4k while filling the filesystem with dd
>> for test generic/274.
> Hi Nirjhar,
>
> The changes look good. With the commit message typo fixed for
> generic/563, feel free to add
>
> Reviewed-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Thanks. Added the RBs, fixed some typos and sent the final [v4].
[v4]
https://lore.kernel.org/all/cover.1756101620.git.nirjhar.roy.lists@gmail.com/
--NR
>
> Regards,
> ojaswin
>
>> [v1] -> [v2]:
>> 1. Removed the patch for btrfs/200 of [v1] - need more analysis on this.
>> 2. Removed the first 2 patches of [v1] which introduced 2 new helper functions
>> 3. btrfs/{137,301} and generic/274 - Instead of scaling the test dynamically
>> based on the underlying disk block size, I have hardcoded the pwrite blocksizes
>> and offsets to 64k which is aligned to all underlying fs block sizes <= 64.
>> 4. For generic/563 - Doubled the iosize instead of btrfs specific hack to cover
>> for btrfs write ranges.
>> 5. Updated the commit messages
>>
>> [v1] - https://lore.kernel.org/all/cover.1753769382.git.nirjhar.roy.lists@gmail.com/
>> [v2] - https://lore.kernel.org/all/cover.1755604735.git.nirjhar.roy.lists@gmail.com/
>>
>> Nirjhar Roy (IBM) (4):
>> btrfs/301: Make the test compatible with all the supported block sizes
>> generic/274: Make the pwrite block sizes and offsets to 64k
>> btrfs/137: Make this test compatible with all supported block sizes
>> generic/563: Increase the iosize to to cover for btrfs
>>
>> tests/btrfs/137 | 11 ++++----
>> tests/btrfs/137.out | 66 ++++++++++++++++++++++-----------------------
>> tests/btrfs/301 | 2 +-
>> tests/generic/274 | 8 +++---
>> tests/generic/563 | 2 +-
>> 5 files changed, 45 insertions(+), 44 deletions(-)
>>
>> --
>> 2.34.1
>>
--
Nirjhar Roy
Linux Kernel Developer
IBM, Bangalore
prev parent reply other threads:[~2025-08-25 6:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 8:15 [PATCH v3 0/4] btrfs: Misc test fixes for large block/node sizes Nirjhar Roy (IBM)
2025-08-20 8:15 ` [PATCH v3 1/4] btrfs/301: Make the test compatible with all the supported block sizes Nirjhar Roy (IBM)
2025-08-22 14:19 ` Disha Goel
2025-08-20 8:15 ` [PATCH v3 2/4] generic/274: Make the pwrite block sizes and offsets to 64k Nirjhar Roy (IBM)
2025-08-22 14:25 ` Disha Goel
2025-08-25 4:34 ` Nirjhar Roy (IBM)
2025-08-25 4:44 ` Qu Wenruo
2025-08-25 6:07 ` Nirjhar Roy (IBM)
2025-08-20 8:15 ` [PATCH v3 3/4] btrfs/137: Make this test compatible with all supported block sizes Nirjhar Roy (IBM)
2025-08-22 14:27 ` Disha Goel
2025-08-20 8:15 ` [PATCH v3 4/4] generic/563: Increase the iosize to to cover for btrfs Nirjhar Roy (IBM)
2025-08-22 14:37 ` Disha Goel
2025-08-25 6:08 ` Nirjhar Roy (IBM)
2025-08-25 5:55 ` [PATCH v3 0/4] btrfs: Misc test fixes for large block/node sizes Ojaswin Mujoo
2025-08-25 6:08 ` Nirjhar Roy (IBM) [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=0ab6b334-a0ba-4797-9aed-c941f9a0b614@gmail.com \
--to=nirjhar.roy.lists@gmail.com \
--cc=djwong@kernel.org \
--cc=fdmanana@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=ritesh.list@gmail.com \
--cc=zlang@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