From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: add basic alignment checks for extent_state
Date: Tue, 28 Jul 2026 16:09:02 +0930 [thread overview]
Message-ID: <cover.1785220613.git.wqu@suse.com> (raw)
Commit 3f255ece2f1e ("btrfs: introduce extra sanity checks for extent
maps") introduced sanity checks for extent maps, but for extent state we
do not have any extra sanity checks.
This series will introduce the check in the 2nd patch, meanwhile the
first one is to fix an exposed unaligned access in extent_fiemap().
Qu Wenruo (2):
btrfs: use proper inclusive end in extent_fiemap()
btrfs: add validation for extent states
fs/btrfs/extent-io-tree.c | 21 +++++++++++++++++++++
fs/btrfs/fiemap.c | 8 ++++----
2 files changed, 25 insertions(+), 4 deletions(-)
--
2.54.0
next reply other threads:[~2026-07-28 6:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 6:39 Qu Wenruo [this message]
2026-07-28 6:39 ` [PATCH 1/2] btrfs: use proper inclusive end in extent_fiemap() Qu Wenruo
2026-07-28 7:35 ` Filipe Manana
2026-07-28 8:48 ` Qu Wenruo
2026-07-28 8:05 ` Daniel Vacek
2026-07-28 8:40 ` Qu Wenruo
2026-07-28 9:17 ` Daniel Vacek
2026-07-28 9:20 ` Qu Wenruo
2026-07-28 9:47 ` Daniel Vacek
2026-07-28 6:39 ` [PATCH 2/2] btrfs: add validation for extent states 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.1785220613.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