From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: minor changes related to btrfs_chunk_map
Date: Fri, 16 Oct 2026 11:18:16 +1030 [thread overview]
Message-ID: <cover.1792111604.git.wqu@suse.com> (raw)
The first two are renames of "stripe_size" to avoid confusion with
"stripe_len". Both names are similar but have completely different
meanings.
The last one is to enhance the chunk map reading to reject overlapping
or different chunk maps from the existing ones.
Qu Wenruo (3):
btrfs: rename btrfs_chunk_map::stripe_size
btrfs: rename stripe_size inside volumes.c
btrfs: reject existing chunks that don't match
fs/btrfs/block-group.c | 4 +-
fs/btrfs/scrub.c | 2 +-
fs/btrfs/tests/extent-map-tests.c | 2 +-
fs/btrfs/volumes.c | 138 +++++++++++++++++-------------
fs/btrfs/volumes.h | 4 +-
5 files changed, 83 insertions(+), 67 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-16 0:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 0:48 Qu Wenruo [this message]
2026-10-16 0:48 ` [PATCH 1/3] btrfs: rename btrfs_chunk_map::stripe_size Qu Wenruo
2026-10-16 0:48 ` [PATCH 2/3] btrfs: rename stripe_size inside volumes.c Qu Wenruo
2026-10-16 0:48 ` [PATCH 3/3] btrfs: reject existing chunks that don't match Qu Wenruo
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.1792111604.git.wqu@suse.com \
--to=wqu@suse.com \
--cc=linux-btrfs@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