From: Shuangpeng <shuangpeng.kernel@gmail.com>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, clm@fb.com, dsterba@suse.com
Subject: Re: [PATCH] btrfs: fix transaction use-after-free in raid stripe insertion
Date: Sun, 16 Aug 2026 22:09:51 -0400 [thread overview]
Message-ID: <501EF29A-2130-40F7-B369-F94A9F3DFE52@gmail.com> (raw)
In-Reply-To: <267b4f65-9afb-4997-ad26-d1ff5addce9f@suse.com>
> On Aug 16, 2026, at 21:58, Qu Wenruo <wqu@suse.com> wrote:
>
>
>
> 在 2026/8/17 10:57, Shuangpeng Bai 写道:
>> If allocation of a RAID stripe extent fails,
>> btrfs_insert_one_raid_extent() aborts and ends the transaction before
>> returning -ENOMEM.
>> btrfs_finish_one_ordered(), the production caller through
>> btrfs_insert_raid_extent(), still owns the transaction handle. It handles
>> the error by aborting the transaction and then reaches the common exit
>> path, which ends the transaction again.
>> The premature end can free the handle and drop its transaction reference.
>> Transaction cleanup can then free the transaction before the caller's
>> second abort accesses the handle and transaction, resulting in
>> use-after-free.
>> Keep the abort at the failure site, but let the caller's common exit path
>> end the transaction once, after it has finished using both objects.
>> Fixes: 02c372e1f016 ("btrfs: add support for inserting raid stripe extents")
>> Cc: stable@vger.kernel.org
>
> Please disclose LLM usage.
>
Hi Qu,
Thanks for pointing this out.
I used Codex to help generate the patch. I had confirmed the bug with KASAN,
and I also verified the proposed fix with my reproducer. With the patch applied,
the reproducer no longer triggers the KASAN report.
I will send a v2 with the appropriate LLM disclosure tag.
Thanks,
Shuangpeng
>> Signed-off-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
>> ---
>> fs/btrfs/raid-stripe-tree.c | 1 -
>> 1 file changed, 1 deletion(-)
>> diff --git a/fs/btrfs/raid-stripe-tree.c b/fs/btrfs/raid-stripe-tree.c
>> index b210371ce91e..89e259a47d8d 100644
>> --- a/fs/btrfs/raid-stripe-tree.c
>> +++ b/fs/btrfs/raid-stripe-tree.c
>> @@ -337,7 +337,6 @@ int btrfs_insert_one_raid_extent(struct btrfs_trans_handle *trans,
>> stripe_extent = kzalloc(item_size, GFP_NOFS);
>> if (unlikely(!stripe_extent)) {
>> btrfs_abort_transaction(trans, -ENOMEM);
>> - btrfs_end_transaction(trans);
>> return -ENOMEM;
>> }
>>
>
next prev parent reply other threads:[~2026-08-17 2:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 1:27 [PATCH] btrfs: fix transaction use-after-free in raid stripe insertion Shuangpeng Bai
2026-08-17 1:58 ` Qu Wenruo
2026-08-17 2:09 ` Shuangpeng [this message]
2026-08-17 2:16 ` Qu Wenruo
2026-08-17 2:15 ` [PATCH v2] " Shuangpeng Bai
2026-08-17 3:04 ` Qu Wenruo
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=501EF29A-2130-40F7-B369-F94A9F3DFE52@gmail.com \
--to=shuangpeng.kernel@gmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.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.