From: Qu Wenruo <wqu@suse.com>
To: pavankumaryalagada@gmail.com, dsterba@suse.com
Cc: mason@kernel.org, fdmanana@suse.com, shuah@kernel.org,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+947286c775f432b073a8@syzkaller.appspotmail.com
Subject: Re: [PATCH] btrfs: fix use-after-free on quota enable allocation failure
Date: Wed, 7 Oct 2026 20:29:14 +1030 [thread overview]
Message-ID: <55739226-436a-42c3-a5fa-c699b01f819e@suse.com> (raw)
In-Reply-To: <4851139b-6cd0-4b1a-9a6e-1af947d49098@suse.com>
在 2026/10/7 19:47, Qu Wenruo 写道:
>
>
> 在 2026/10/7 19:36, pavankumaryalagada@gmail.com 写道:
>> From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>>
>> The quota root remains on the transaction's dirty root list when
>> kzalloc_obj() fails and btrfs_quota_enable() releases it without
>> aborting the transaction. Later add_root_to_dirty_list() then accesses
>> the freed dirty_list, causing a slab-use-after-free.
>>
>> Abort the transaction on allocation failure to clean up the dirty
>> root before releasing the quota root.
>>
>> Reported-by: syzbot+947286c775f432b073a8@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=947286c775f432b073a8
>> Fixes: 8d54518b5e52 ("btrfs: qgroup: pre-allocate btrfs_qgroup to
>> reduce GFP_ATOMIC usage")
>> Signed-off-by: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>
> Reviewed-by: Qu Wenruo <wqu@suse.com>
My bad, Sashiko exposed a valid but very rare race that the temporary
quota_root can be added to fs_info->dirty_cowonly_roots list.
This requires enough subvolumes to make quota_root to be higher than
level 0 in the first place, which is not common but definitely possible.
Although all readers of fs_info->dirty_cowonly_roots won't be reached
after the transaction is aborted, there is still a very small window
that another thread is already holding a trans handler just after the
transaction is aborted and the quota root is freed.
In that case the other thread may access the already freed quota_root
through fs_info->dirty_cowonly_roots->next.
I'm afraid we need to call list_del("a_root->dirty_list) with proper
trans_lock hold during error handling.
>
>> ---
>> fs/btrfs/qgroup.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/fs/btrfs/qgroup.c b/fs/btrfs/qgroup.c
>> index f68b696b4bf7..42be06675c90 100644
>> --- a/fs/btrfs/qgroup.c
>> +++ b/fs/btrfs/qgroup.c
>> @@ -1204,6 +1204,7 @@ int btrfs_quota_enable(struct btrfs_fs_info
>> *fs_info,
>> prealloc = kzalloc_obj(*prealloc, GFP_NOFS);
>> if (!prealloc) {
>> ret = -ENOMEM;
>> + btrfs_abort_transaction(trans, ret);
>> goto out_free_path;
>> }
>> qgroup = add_qgroup_rb(fs_info, prealloc, BTRFS_FS_TREE_OBJECTID);
>
next prev parent reply other threads:[~2026-10-07 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 9:06 pavankumaryalagada
2026-10-07 9:17 ` Qu Wenruo
2026-10-07 9:22 ` Qu Wenruo
2026-10-07 9:59 ` Qu Wenruo [this message]
2026-10-07 11:55 ` Yalagada Pavan Kumar
2026-10-07 20:58 ` 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=55739226-436a-42c3-a5fa-c699b01f819e@suse.com \
--to=wqu@suse.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=pavankumaryalagada@gmail.com \
--cc=shuah@kernel.org \
--cc=syzbot+947286c775f432b073a8@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®