From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: enhance error handling of __free_extent()
Date: Mon, 24 Nov 2025 14:45:25 +1030 [thread overview]
Message-ID: <cover.1763957608.git.wqu@suse.com> (raw)
There is a github bug report about btrfs-convert crash, where
btrfs_print_leaf() is called on NULL path->nodes[0].
The first patch fix the bug by cross-port a fix from kernel part.
The second patch refactor the error handling of __free_extent(), mostly
follow the kernel patch "btrfs: refactor the error handling of __btrfs_free_extent()".
Qu Wenruo (2):
btrfs-progs: do not dump leaf if the path is released inside
__free_extent()
btrfs-progs: btrfs: refactor the error handling of __free_extent()
kernel-shared/extent-tree.c | 154 ++++++++++++++++++------------------
1 file changed, 75 insertions(+), 79 deletions(-)
--
2.52.0
next reply other threads:[~2025-11-24 4:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-24 4:15 Qu Wenruo [this message]
2025-11-24 4:15 ` [PATCH 1/2] btrfs-progs: do not dump leaf if the path is released inside __free_extent() Qu Wenruo
2025-11-24 4:15 ` [PATCH 2/2] btrfs-progs: btrfs: refactor the error handling of __free_extent() Qu Wenruo
2025-11-25 17:05 ` [PATCH 0/2] btrfs-progs: enhance " Boris Burkov
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.1763957608.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