From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: dsterba@suse.cz, Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org,
syzbot+772bdfe41846e057fa83@syzkaller.appspotmail.com
Subject: Re: [PATCH] btrfs: fix a use-after-free race if btrfs_open_devices() failed
Date: Fri, 27 Jun 2025 12:07:27 +0930 [thread overview]
Message-ID: <8d6000bf-9317-4ccb-9383-a466a574df83@gmx.com> (raw)
In-Reply-To: <20250627010918.GD31241@twin.jikos.cz>
在 2025/6/27 10:39, David Sterba 写道:
> On Fri, Jun 27, 2025 at 09:52:58AM +0930, Qu Wenruo wrote:
>> [BUG]
>> With the latest v5 version patchset "btrfs: use fs_holder_ops for btrfs"
>> merged into linux-next, syzbot reported an use-after-free:
> ...
>> This will be folded into the patch "btrfs: delay btrfs_open_devices()
>> until super block is created".
>
> Thanks, patch added to linux-next branch on top of the series for
> clarity, for the next iteration it can be folded.
>
It turns out there are more locations needs similar handling.
I'll need to send out a v2 update for this hot fix unfortunately...
prev parent reply other threads:[~2025-06-27 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 0:22 [PATCH] btrfs: fix a use-after-free race if btrfs_open_devices() failed Qu Wenruo
2025-06-27 1:09 ` David Sterba
2025-06-27 2:37 ` Qu Wenruo [this message]
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=8d6000bf-9317-4ccb-9383-a466a574df83@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=syzbot+772bdfe41846e057fa83@syzkaller.appspotmail.com \
--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