From: Qu Wenruo <wqu@suse.com>
To: Shuangpeng Bai <shuangpeng.kernel@gmail.com>,
linux-btrfs@vger.kernel.org
Cc: clm@fb.com, dsterba@suse.com
Subject: Re: [PATCH v2] btrfs: fix transaction use-after-free in raid stripe insertion
Date: Mon, 17 Aug 2026 12:34:02 +0930 [thread overview]
Message-ID: <8e48e984-4df3-4b4e-b812-4b7f20f013b7@suse.com> (raw)
In-Reply-To: <20260817021512.3010812-1-shuangpeng.kernel@gmail.com>
在 2026/8/17 11:45, 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
> Assisted-by: Codex:GPT-5
> Signed-off-by: Shuangpeng Bai <shuangpeng.kernel@gmail.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
> ---
> Changes in v2:
> - Add the Assisted-by tag to disclose LLM usage.
>
> v1: https://lore.kernel.org/r/20260817012733.2962781-1-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;
> }
>
prev parent reply other threads:[~2026-08-17 3:04 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
2026-08-17 2:16 ` Qu Wenruo
2026-08-17 2:15 ` [PATCH v2] " Shuangpeng Bai
2026-08-17 3:04 ` 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=8e48e984-4df3-4b4e-b812-4b7f20f013b7@suse.com \
--to=wqu@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=shuangpeng.kernel@gmail.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