From: fdmanana@kernel.org
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/3] btrfs: improve sibling keys check failure report
Date: Wed, 26 Apr 2023 11:51:34 +0100 [thread overview]
Message-ID: <cover.1682505780.git.fdmanana@suse.com> (raw)
From: Filipe Manana <fdmanana@suse.com>
This makes reporting of sibling key check failures more useful, by
printing more exact stack traces in case the extent buffers are leaves
and dumping the extent buffers. This is motivated by a recent report [1].
More details on the changelogs of each patch.
[1] https://lore.kernel.org/linux-btrfs/20230423222213.5391.409509F4@e16-tech.com/
Filipe Manana (3):
btrfs: abort transaction when sibling keys check fails for leaves
btrfs: print extent buffers when sibling keys check fails
btrfs: tag as unlikely the key comparison when checking sibling keys
fs/btrfs/ctree.c | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
--
2.34.1
next reply other threads:[~2023-04-26 10:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-26 10:51 fdmanana [this message]
2023-04-26 10:51 ` [PATCH 1/3] btrfs: abort transaction when sibling keys check fails for leaves fdmanana
2023-04-26 11:18 ` Qu Wenruo
2023-04-26 10:51 ` [PATCH 2/3] btrfs: print extent buffers when sibling keys check fails fdmanana
2023-04-26 11:20 ` Qu Wenruo
2023-04-26 11:31 ` Filipe Manana
2023-04-26 11:40 ` Qu Wenruo
2023-04-26 11:44 ` Filipe Manana
2023-04-26 11:50 ` Qu Wenruo
2023-04-26 12:00 ` Filipe Manana
2023-04-27 23:00 ` David Sterba
2023-04-26 10:51 ` [PATCH 3/3] btrfs: tag as unlikely the key comparison when checking sibling keys fdmanana
2023-04-26 11:21 ` Qu Wenruo
2023-04-27 23:13 ` David Sterba
2023-04-27 23:13 ` [PATCH 0/3] btrfs: improve sibling keys check failure report 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.1682505780.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