From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Cc: Ritesh Harjani <ritesh.list@gmail.com>,
Zhang Yi <yi.zhang@huawei.com>,
linux-kernel@vger.kernel.org,
"Darrick J . Wong" <djwong@kernel.org>
Subject: [PATCH 0/2] Some more misc fsmap fixes
Date: Fri, 5 Sep 2025 13:44:45 +0530 [thread overview]
Message-ID: <cover.1757058211.git.ojaswin@linux.ibm.com> (raw)
These 2 patches mostly fixup a couple edge case inconsistent behavior
we were seeing in fsmap. Further, convert fsmap path to use block size
units wherever possible to avoid issues due to block to cluster to block
conversions like [1].
[1] https://lore.kernel.org/linux-ext4/e7472c8535c9c5ec10f425f495366864ea12c9da.1754377641.git.ojaswin@linux.ibm.com/
Tested with some custom edge cases (which I'll see how to consistently
convert to xfstests) as well as generic/365 on 4k, 64k and bigalloc
Ojaswin Mujoo (2):
ext4: Correctly handle queries for metadata mappings
fsmap: use blocksize units instead of cluster units
fs/ext4/fsmap.c | 56 +++++++++++++++++++++++++++--------------------
fs/ext4/mballoc.c | 25 ++++++++++++++-------
2 files changed, 49 insertions(+), 32 deletions(-)
--
2.49.0
next reply other threads:[~2025-09-05 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 8:14 Ojaswin Mujoo [this message]
2025-09-05 8:14 ` [PATCH 1/2] ext4: Correctly handle queries for metadata mappings Ojaswin Mujoo
2025-09-05 8:14 ` [PATCH 2/2] fsmap: use blocksize units instead of cluster units Ojaswin Mujoo
2025-09-26 12:35 ` Theodore Ts'o
2025-10-02 17:42 ` Ojaswin Mujoo
2025-09-26 21:47 ` [PATCH 0/2] Some more misc fsmap fixes Theodore Ts'o
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.1757058211.git.ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=djwong@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
/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
all inboxes | Powered by JetHome®