From: Qu Wenruo <wqu@suse.com>
To: Deepanshu Kartikey <kartikey406@gmail.com>,
clm@fb.com, dsterba@suse.com, miaox@cn.fujitsu.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com
Subject: Re: [PATCH] btrfs: fix memory leak of fs_devices in degraded seed device path
Date: Fri, 12 Dec 2025 10:25:17 +1030 [thread overview]
Message-ID: <123e2014-59e0-4c0a-905f-c2fee4455eb8@suse.com> (raw)
In-Reply-To: <20251210132807.3263207-1-kartikey406@gmail.com>
在 2025/12/10 23:58, Deepanshu Kartikey 写道:
> In open_seed_devices(), when find_fsid() fails and we're in DEGRADED
> mode, a new fs_devices is allocated via alloc_fs_devices() but is never
> added to the seed_list before returning. This contrasts with the normal
> path where fs_devices is properly added via list_add().
>
> If any error occurs later in read_one_dev() or btrfs_read_chunk_tree(),
> the cleanup code iterates seed_list to free seed devices, but this
> orphaned fs_devices is never found and never freed, causing a memory
> leak. Any devices allocated via add_missing_dev() and attached to this
> fs_devices are also leaked.
>
> Fix this by adding the newly allocated fs_devices to seed_list in the
> degraded path, consistent with the normal path.
>
> Fixes: 5f37583569442 ("Btrfs: move the missing device to its own fs device list")
> Reported-by: syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=eadd98df8bceb15d7fed
> Tested-by: syzbot+eadd98df8bceb15d7fed@syzkaller.appspotmail.com
> Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> fs/btrfs/volumes.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index ae1742a35e76..13c514684cfb 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -7128,6 +7128,7 @@ static struct btrfs_fs_devices *open_seed_devices(struct btrfs_fs_info *fs_info,
>
> fs_devices->seeding = true;
> fs_devices->opened = 1;
> + list_add(&fs_devices->seed_list, &fs_info->fs_devices->seed_list);
> return fs_devices;
> }
>
prev parent reply other threads:[~2025-12-11 23:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 13:28 [PATCH] btrfs: fix memory leak of fs_devices in degraded seed device path Deepanshu Kartikey
2025-12-11 18:48 ` David Sterba
2025-12-11 23:55 ` 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=123e2014-59e0-4c0a-905f-c2fee4455eb8@suse.com \
--to=wqu@suse.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=kartikey406@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaox@cn.fujitsu.com \
--cc=syzbot+eadd98df8bceb15d7fed@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