From: Teng Liu <27rabbitlt@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, AHN SEOK-YOUNG <iamsyahn@gmail.com>
Subject: Re: [PATCH] btrfs: warn about extent buffer that can not be released
Date: Thu, 9 Apr 2026 00:18:15 +0200 [thread overview]
Message-ID: <adbTGR5OfU6Bxfsw@rabbitArch> (raw)
In-Reply-To: <1c3a439e1e21c4ee32575b264ac0bc3935ea4f53.1775364843.git.wqu@suse.com>
On 2026-04-05 14:26, Qu Wenruo wrote:
>
> Meanwhile if Ahn or Teng can give this patch a try for the existing
> use-after-free problem, it would be appreciated a lot.
I tested t his patch on a QEMU VM (kernel 7.0.0.-rc4 + this patch) with
a forged corrupted btrfs image.
With the patch, it fails gracefully:
[root@btrfs-test ~]# mount /dev/sda /mnt
[ 107.497290] BTRFS error (device sda): parent transid verify failed on logical 1081344 mirror 1 wanted 5 found 1
...
[ 108.302268] BTRFS error (device sda): parent transid verify failed on logical 1228800 mirror 1 wanted 5 found 2
[ 108.302730] BTRFS error (device sda): bad tree block start, mirror 1 want 1245184 have 0
...
[ 108.306296] BTRFS error (device sda): bad tree block start, mirror 1 want 1392640 have 0
[ 109.098136] BTRFS error (device sda): devid 999 uuid 00000000-0000-0000-0000-000000000000 is missing
[ 109.099635] BTRFS error (device sda): failed to read chunk tree: -2
[ 109.998476] BTRFS error (device sda): open_ctree failed: -2
mount: /mnt: fsconfig() failed: No such file or directory.
dmesg(1) may have more information after failed mount system call.
No panic observed. Thanks!
Tested-by: Teng Liu <27rabbitlt@gmail.com>
next prev parent reply other threads:[~2026-04-08 22:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-05 4:56 [PATCH] btrfs: warn about extent buffer that can not be released Qu Wenruo
2026-04-05 10:05 ` 말란말야
2026-04-08 22:18 ` Teng Liu [this message]
2026-04-15 11:25 ` Filipe Manana
2026-04-15 23:02 ` Qu Wenruo
2026-04-16 10:22 ` Filipe Manana
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=adbTGR5OfU6Bxfsw@rabbitArch \
--to=27rabbitlt@gmail.com \
--cc=iamsyahn@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.