From: "Naohiro Aota" <Naohiro.Aota@wdc.com>
To: "Guangshuo Li" <lgs201920130244@gmail.com>,
"Chris Mason" <clm@fb.com>, "David Sterba" <dsterba@suse.com>,
"Naohiro Aota" <naohiro.aota@wdc.com>,
"Johannes Thumshirn" <johannes.thumshirn@wdc.com>,
<linux-btrfs@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] btrfs: fix zoned sub_group leak on space_info sysfs failure
Date: Fri, 05 Jun 2026 11:22:43 +0900 [thread overview]
Message-ID: <DJ0RAMUVW89X.C3T31TKENNYN@wdc.com> (raw)
In-Reply-To: <20260604121043.1425201-1-lgs201920130244@gmail.com>
On Thu Jun 4, 2026 at 9:10 PM JST, Guangshuo Li wrote:
> On zoned filesystems, create_space_info() creates a space_info sub_group
> before registering the parent space_info in sysfs.
>
> If the sub_group registration succeeds but the parent
> btrfs_sysfs_add_space_info_type() call fails, the parent space_info is
> released through its kobject release path, but the already published
> sub_group is left behind. The sub_group also keeps its logical parent
> pointer, which then points at freed memory.
>
> Remember the created sub_group before registering the parent and remove it
> when parent sysfs registration fails. Cache the sub_group pointer before
> calling btrfs_sysfs_add_space_info_type(), as that helper may already have
> put and released the parent on failure.
Thank you for the patch. The logic itself is correct, but I think there
is a better alternative. My suggestion is making
btrfs_sysfs_remove_space_info() responsible for removing sub-groups (if
any) first.
With that change, we can reverse the space-info creation order in
create_space_info(). If the parent space-info registration fails, no
sub-groups exist yet, so nothing extra needs to be cleaned up. If
sub-group creation fails, we can call btrfs_sysfs_remove_space_info() on
the parent to clean everything up.
This change also has a side benefit. Currently,
check_removing_space_info() is also removing sub-groups, which
contradicts its name. We can remove those
btrfs_sysfs_remove_space_info() calls for sub-groups from the function,
making it a pure checker.
>
> Fixes: f92ee31e031c7 ("btrfs: introduce btrfs_space_info sub-group")
> Signed-off-by: Guangshuo Li <lgs201920130244@gmail.com>
> ---
> fs/btrfs/space-info.c | 7 ++++++-
> 1 file changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/space-info.c b/fs/btrfs/space-info.c
> index f0436eea1544..03659dfcb830 100644
> --- a/fs/btrfs/space-info.c
> +++ b/fs/btrfs/space-info.c
> @@ -296,6 +296,7 @@ static int create_space_info(struct btrfs_fs_info *info, u64 flags)
> {
>
> struct btrfs_space_info *space_info;
> + struct btrfs_space_info *sub_group = NULL;
> int ret = 0;
>
> space_info = kzalloc_obj(*space_info, GFP_NOFS);
> @@ -316,11 +317,15 @@ static int create_space_info(struct btrfs_fs_info *info, u64 flags)
>
> if (ret)
> goto out_free;
> + sub_group = space_info->sub_group[0];
> }
>
> ret = btrfs_sysfs_add_space_info_type(space_info);
> - if (ret)
> + if (ret) {
> + if (sub_group)
> + btrfs_sysfs_remove_space_info(sub_group);
> return ret;
> + }
>
> list_add(&space_info->list, &info->space_info);
> if (flags & BTRFS_BLOCK_GROUP_DATA)
next prev parent reply other threads:[~2026-06-05 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-04 12:10 Guangshuo Li
2026-06-05 2:22 ` Naohiro Aota [this message]
2026-06-09 15:06 ` Guangshuo Li
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=DJ0RAMUVW89X.C3T31TKENNYN@wdc.com \
--to=naohiro.aota@wdc.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=johannes.thumshirn@wdc.com \
--cc=lgs201920130244@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®