From: "Nirjhar Roy (IBM)" <nirjhar.roy.lists@gmail.com>
To: fstests@vger.kernel.org
Cc: linux-btrfs@vger.kernel.org, nirjhar.roy.lists@gmail.com,
ritesh.list@gmail.com, ojaswin@linux.ibm.com, djwong@kernel.org,
fdmanana@kernel.org, quwenruo.btrfs@gmx.com, zlang@kernel.org
Subject: [PATCH v2 0/3] btrfs: More test fixes for large block/node sizes
Date: Mon, 13 Oct 2025 05:39:41 +0000 [thread overview]
Message-ID: <cover.1760332925.git.nirjhar.roy.lists@gmail.com> (raw)
More btrfs test fixes. These tests were ran with 64k block size and they failed.
Individual patches have the details. A previous patch series with some other
test fixes was posted[1].
[v1] -> v2
1. Removed the patch for generic/371 (will send it in a separate series)
2. Added RB by Filipe in generic/562
3. Added RBs by Filipe and Zorro in btrfs/200
4. For btrfs/290 - Commit message changes and changing "196608" and "65536" to
"192k" and "64k" respectively in the test script to make it more readable
(Suggested by Filipe).
[1] https://lore.kernel.org/all/cover.1756101620.git.nirjhar.roy.lists@gmail.com/
[v1] https://lore.kernel.org/all/cover.1758036285.git.nirjhar.roy.lists@gmail.com/
Nirjhar Roy (IBM) (3):
generic/562: Make test compatible with block sizes till 64k
btrfs/200: Make the test compatible with all supported block sizes
btrfs/290: Make the test compatible with all supported block sizes
tests/btrfs/200 | 8 ++++----
tests/btrfs/200.out | 8 ++++----
tests/btrfs/290 | 16 ++++++++--------
tests/generic/562 | 2 +-
4 files changed, 17 insertions(+), 17 deletions(-)
--
2.34.1
next reply other threads:[~2025-10-13 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 5:39 Nirjhar Roy (IBM) [this message]
2025-10-13 5:39 ` [PATCH v2 1/3] generic/562: Make test compatible with block sizes till 64k Nirjhar Roy (IBM)
2025-10-13 5:39 ` [PATCH v2 2/3] btrfs/200: Make the test compatible with all supported block sizes Nirjhar Roy (IBM)
2025-10-13 5:39 ` [PATCH v2 3/3] btrfs/290: " Nirjhar Roy (IBM)
2025-10-21 4:44 ` Nirjhar Roy (IBM)
2025-10-21 11:49 ` Filipe Manana
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.1760332925.git.nirjhar.roy.lists@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 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.