mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Jiasheng Jiang <jiashengjiangcool@gmail.com>,
	Chris Mason <clm@fb.com>, David Sterba <dsterba@suse.com>,
	Jeff Mahoney <jeffm@suse.com>, Liu Bo <bo.li.liu@oracle.com>,
	Nikolay Borisov <nborisov@suse.com>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix memory leaks in create_space_info error paths
Date: Mon, 12 Jan 2026 07:36:29 +1030	[thread overview]
Message-ID: <2539a74d-9276-4b82-8e67-80581ff7dcb9@suse.com> (raw)
In-Reply-To: <20260111192037.20932-1-jiashengjiangcool@gmail.com>



在 2026/1/12 05:50, Jiasheng Jiang 写道:
> In create_space_info(), the 'space_info' object is allocated at the
> beginning of the function. However, there are two error paths where the
> function returns an error code without freeing the allocated memory:
> 
> 1. When create_space_info_sub_group() fails in zoned mode.
> 2. When btrfs_sysfs_add_space_info_type() fails.
> 
> In both cases, 'space_info' has not yet been added to the
> fs_info->space_info list, resulting in a memory leak. Fix this by
> adding an error handling label to kfree(space_info) before returning.
> 
> Fixes: 2be12ef79fe9 ("btrfs: Separate space_info create/update")
> Signed-off-by: Jiasheng Jiang <jiashengjiangcool@gmail.com>

Reviewed-by: Qu Wenruo <wqu@suse.com>

Thanks,
Qu

> ---
>   fs/btrfs/space-info.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/btrfs/space-info.c b/fs/btrfs/space-info.c
> index 6babbe333741..3f08e450f796 100644
> --- a/fs/btrfs/space-info.c
> +++ b/fs/btrfs/space-info.c
> @@ -306,18 +306,22 @@ static int create_space_info(struct btrfs_fs_info *info, u64 flags)
>   							  0);
>   
>   		if (ret)
> -			return ret;
> +			goto out_free;
>   	}
>   
>   	ret = btrfs_sysfs_add_space_info_type(space_info);
>   	if (ret)
> -		return ret;
> +		goto out_free;
>   
>   	list_add(&space_info->list, &info->space_info);
>   	if (flags & BTRFS_BLOCK_GROUP_DATA)
>   		info->data_sinfo = space_info;
>   
>   	return ret;
> +
> +out_free:
> +	kfree(space_info);
> +	return ret;
>   }
>   
>   int btrfs_init_space_info(struct btrfs_fs_info *fs_info)


      reply	other threads:[~2026-01-11 21:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-11 19:20 Jiasheng Jiang
2026-01-11 21:06 ` 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=2539a74d-9276-4b82-8e67-80581ff7dcb9@suse.com \
    --to=wqu@suse.com \
    --cc=bo.li.liu@oracle.com \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=jeffm@suse.com \
    --cc=jiashengjiangcool@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nborisov@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 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®