From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/5] btrfs: tag as unlikely several unexpected critical errors
Date: Wed, 17 Sep 2025 08:52:37 +0100 [thread overview]
Message-ID: <cover.1758095164.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
Several critical error checks are never expected to be hit, so tag them
as unlikely. Details in the changelogs.
Filipe Manana (5):
btrfs: store and use node size in local variable in check_eb_alignment()
btrfs: mark extent buffer alignment checks as unlikely
btrfs: mark as unlikely not uptodate check in read_extent_buffer_pages()
btrfs: mark as unlikely not uptodate extent buffer checks when navigating btrees
btrfs: mark leaf space and overflow checks as unlikely on insert and extension
fs/btrfs/ctree.c | 22 +++++++++++-----------
fs/btrfs/extent_io.c | 21 +++++++++++----------
2 files changed, 22 insertions(+), 21 deletions(-)
--
2.47.2
next reply other threads:[~2025-09-17 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 7:52 fdmanana [this message]
2025-09-17 7:52 ` [PATCH 1/5] btrfs: store and use node size in local variable in check_eb_alignment() fdmanana
2025-09-17 7:52 ` [PATCH 2/5] btrfs: mark extent buffer alignment checks as unlikely fdmanana
2025-09-17 7:52 ` [PATCH 3/5] btrfs: mark as unlikely not uptodate check in read_extent_buffer_pages() fdmanana
2025-09-17 7:52 ` [PATCH 4/5] btrfs: mark as unlikely not uptodate extent buffer checks when navigating btrees fdmanana
2025-09-17 7:52 ` [PATCH 5/5] btrfs: mark leaf space and overflow checks as unlikely on insert and extension fdmanana
2025-09-17 9:15 ` [PATCH 0/5] btrfs: tag as unlikely several unexpected critical errors Qu Wenruo
2025-09-17 17:09 ` David Sterba
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.1758095164.git.fdmanana@suse.com \
--to=fdmanana@kernel.org \
--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