From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs: small improvement to leaf dump
Date: Thu, 27 Apr 2023 20:16:26 +0800 [thread overview]
Message-ID: <cover.1682597619.git.wqu@suse.com> (raw)
The first patch is just constify the tree dump infrastructure, exposed
during the development.
The second patch is the main dish, inspired by a report that turns out
to be bitflip in extent tree.
However the leaf dump in dmesg is pretty large (100+ slots), needs to
manually search the leaf using the bytenr from the error messages.
Thus if we can output the slot number, it would be much easier to locate
the problem, just like what we did in tree-checker.
Qu Wenruo (2):
btrfs: print-tree: accept const extent buffer pointer
btrfs: improve leaf dump and error handling
fs/btrfs/ctree.c | 8 +--
fs/btrfs/ctree.h | 2 +-
fs/btrfs/extent-tree.c | 125 +++++++++++++++++++----------------------
fs/btrfs/print-tree.c | 16 +++---
fs/btrfs/print-tree.h | 4 +-
5 files changed, 73 insertions(+), 82 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-27 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 12:16 Qu Wenruo [this message]
2023-04-27 12:16 ` [PATCH 1/2] btrfs: print-tree: accept const extent buffer pointer Qu Wenruo
2023-04-27 12:16 ` [PATCH 2/2] btrfs: improve leaf dump and error handling Qu Wenruo
2023-05-02 15:34 ` [PATCH 0/2] btrfs: small improvement to leaf dump 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.1682597619.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