From: "David Hildenbrand (Arm)" <david@kernel.org>
To: ranxiaokai627@163.com, akpm@linux-foundation.org, ljs@kernel.org,
ziy@nvidia.com, baolin.wang@linux.alibaba.com,
liam@infradead.org, npache@redhat.com, ryan.roberts@arm.com,
dev.jain@arm.com, baohua@kernel.org, lance.yang@linux.dev
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ran Xiaokai <ran.xiaokai@zte.com.cn>
Subject: Re: [PATCH] mm/huge_memory: fix memory leak when kobject_init_and_add() fails
Date: Tue, 9 Jun 2026 15:19:03 +0200 [thread overview]
Message-ID: <c9500789-5a27-4348-84b6-a787230edebf@kernel.org> (raw)
In-Reply-To: <20260609131249.89288-1-ranxiaokai627@163.com>
On 6/9/26 15:12, ranxiaokai627@163.com wrote:
> From: Ran Xiaokai <ran.xiaokai@zte.com.cn>
>
> As documented in the comments for kobject_init_and_add():
>
> "If this function returns an error, kobject_put() must be called to
> properly clean up the memory associated with the object. This is the
> same type of error handling after a call to kobject_add() and kobject
> lifetime rules are the same here."
>
> This is because kobject_init_and_add() may have already allocated memory
> internally for the kobject name (kobj->name), and leaving the refcount
> at 1 prevents its release callback from being triggered.
>
> Fixes: 3485b88390b0a ("mm: thp: introduce multi-size THP sysfs interface")
> Signed-off-by: Ran Xiaokai <ran.xiaokai@zte.com.cn>
> ---
> mm/huge_memory.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
> index 653f2dc03403..601750dbe79f 100644
> --- a/mm/huge_memory.c
> +++ b/mm/huge_memory.c
> @@ -790,11 +790,8 @@ static struct thpsize *thpsize_create(int order, struct kobject *parent)
>
> ret = kobject_init_and_add(&thpsize->kobj, &thpsize_ktype, parent,
> "hugepages-%lukB", size);
> - if (ret) {
> - kfree(thpsize);
> - goto err;
> - }
> -
> + if (ret)
> + goto err_put;
>
> ret = sysfs_add_group(&thpsize->kobj, &any_ctrl_attr_grp);
> if (ret)
This looks a lot like:
https://lore.kernel.org/all/20260411062152.2092967-1-lgs201920130244@gmail.com/
--
Cheers,
David
next prev parent reply other threads:[~2026-06-09 13:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 13:12 ranxiaokai627
2026-06-09 13:19 ` David Hildenbrand (Arm) [this message]
2026-06-09 14:04 ` Lance Yang
2026-06-09 14:20 ` Lorenzo Stoakes
2026-06-10 0:28 ` SeongJae Park
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=c9500789-5a27-4348-84b6-a787230edebf@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=npache@redhat.com \
--cc=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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®