From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Sachi King <nakato@nakato.io>, u-boot@lists.denx.de
Cc: kabel@kernel.org, wqu@suse.com, linux-btrfs@vger.kernel.org
Subject: Re: BTRFS use-after-free bug at free_extent_buffer_internal
Date: Mon, 22 Apr 2024 18:25:58 +0930 [thread overview]
Message-ID: <9086a324-b17a-4e00-906b-816fb2b05880@gmx.com> (raw)
In-Reply-To: <995dd168-8e1e-4b99-896c-ece4dc88d6e9@gmx.com>
在 2024/4/22 16:45, Qu Wenruo 写道:
[...]
>>
>> I added a print statement to free_extent_buffer_internal that prints the
>> start address of the extent_buffer as I'm not sure what to be looking for
>> here. This print statement is before the decrement.
>>> printf("free_extent_buffer_internal: eb->start[%llx] eb->refs[%i]\n",
>>> eb->start, eb->refs);
>>
Just a small advice, in fact you can go with sandbox mode, running
U-boot in userspace, and bind a host file as a device to test the
filesystem code.
At least that's what I did for most U-boot bugs.
Thanks,
Qu
next prev parent reply other threads:[~2024-04-22 8:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 6:37 BTRFS use-after-free bug at free_extent_buffer_internal Sachi King
2024-04-22 7:15 ` Qu Wenruo
2024-04-22 8:55 ` Qu Wenruo [this message]
2024-04-23 4:53 ` Sachi King
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=9086a324-b17a-4e00-906b-816fb2b05880@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=kabel@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=nakato@nakato.io \
--cc=u-boot@lists.denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox