From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Haoxiang Li <haoxiang_li2024@163.com>,
clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
fdmanana@suse.com
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: fix a memory leak issue in read_one_chunk()
Date: Mon, 3 Mar 2025 14:54:17 +1030 [thread overview]
Message-ID: <31e5c235-4e59-4b37-ab3e-db05012d7119@gmx.com> (raw)
In-Reply-To: <20250303024233.3865292-1-haoxiang_li2024@163.com>
在 2025/3/3 13:12, Haoxiang Li 写道:
> Add btrfs_free_chunk_map() to free the memory allocated
> by btrfs_alloc_chunk_map() if btrfs_add_chunk_map() fails.
>
> Fixes: 7dc66abb5a47 ("btrfs: use a dedicated data structure for chunk maps")
> Cc: stable@vger.kernel.org
> Signed-off-by: Haoxiang Li <haoxiang_li2024@163.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
And the fixes tag is also correct, before that commit, add_extent_map()
will increase the ref if tree_insert() succeeded, thus if it failed the
unconditional free_extent_map() will just free the no longer utilized em.
But at that commit, we no longer has that feature, thus has to manually
cleanup the map.
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 fb22d4425cb0..3f8afbd1ebb5 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -7155,6 +7155,7 @@ static int read_one_chunk(struct btrfs_key *key, struct extent_buffer *leaf,
> btrfs_err(fs_info,
> "failed to add chunk map, start=%llu len=%llu: %d",
> map->start, map->chunk_len, ret);
> + btrfs_free_chunk_map(map);
> }
>
> return ret;
next prev parent reply other threads:[~2025-03-03 4:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 2:42 Haoxiang Li
2025-03-03 4:24 ` Qu Wenruo [this message]
2025-03-05 11:53 ` Filipe Manana
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=31e5c235-4e59-4b37-ab3e-db05012d7119@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=haoxiang_li2024@163.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@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®