From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Rakie Kim <rakie.kim@sk.com>
Cc: <akpm@linux-foundation.org>, <gourry@gourry.net>,
<linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>, <joshua.hahnjy@gmail.com>,
<dan.j.williams@intel.com>, <ying.huang@linux.alibaba.com>,
<david@redhat.com>, <osalvador@suse.de>,
<kernel_team@skhynix.com>, <honggyu.kim@sk.com>,
<yunjeong.mun@sk.com>
Subject: Re: [PATCH v7 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs
Date: Tue, 15 Apr 2025 16:41:45 +0100 [thread overview]
Message-ID: <20250415164145.00005b6f@huawei.com> (raw)
In-Reply-To: <20250408073243.488-2-rakie.kim@sk.com>
On Tue, 8 Apr 2025 16:32:40 +0900
Rakie Kim <rakie.kim@sk.com> wrote:
> Memory leaks occurred when removing sysfs attributes for weighted
> interleave. Improper kobject deallocation led to unreleased memory
> when initialization failed or when nodes were removed.
>
> This patch resolves the issue by replacing unnecessary `kfree()`
> calls with proper `kobject_del()` and `kobject_put()` sequences,
> ensuring correct teardown and preventing memory leaks.
>
> By explicitly calling `kobject_del()` before `kobject_put()`,
> the release function is now invoked safely, and internal sysfs
> state is correctly cleaned up. This guarantees that the memory
> associated with the kobject is fully released and avoids
> resource leaks, thereby improving system stability.
>
> Fixes: dce41f5ae253 ("mm/mempolicy: implement the sysfs-based weighted_interleave interface")
> Signed-off-by: Rakie Kim <rakie.kim@sk.com>
> Signed-off-by: Honggyu Kim <honggyu.kim@sk.com>
> Signed-off-by: Yunjeong Mun <yunjeong.mun@sk.com>
> Reviewed-by: Gregory Price <gourry@gourry.net>
LGTM
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
next prev parent reply other threads:[~2025-04-15 15:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:32 [PATCH v7 0/3] Enhance sysfs handling for memory hotplug in weighted interleave Rakie Kim
2025-04-08 7:32 ` [PATCH v7 1/3] mm/mempolicy: Fix memory leaks in weighted interleave sysfs Rakie Kim
2025-04-08 13:45 ` Joshua Hahn
2025-04-15 15:41 ` Jonathan Cameron [this message]
2025-04-08 7:32 ` [PATCH v7 2/3] mm/mempolicy: Prepare weighted interleave sysfs for memory hotplug Rakie Kim
2025-04-08 13:49 ` Joshua Hahn
2025-04-09 3:43 ` Dan Williams
2025-04-09 3:54 ` Dan Williams
2025-04-09 5:56 ` Rakie Kim
2025-04-09 18:51 ` Dan Williams
2025-04-10 7:53 ` Rakie Kim
2025-04-10 8:06 ` Rakie Kim
2025-04-11 3:11 ` Andrew Morton
2025-04-11 7:21 ` Rakie Kim
2025-04-11 22:24 ` Dan Williams
2025-04-08 7:32 ` [PATCH v7 3/3] mm/mempolicy: Support memory hotplug in weighted interleave Rakie Kim
2025-04-08 13:52 ` Joshua Hahn
2025-04-08 14:45 ` Gregory Price
2025-04-09 9:05 ` David Hildenbrand
2025-04-09 11:39 ` Honggyu Kim
2025-04-09 11:52 ` David Hildenbrand
2025-04-10 7:53 ` Rakie Kim
2025-04-10 13:25 ` Honggyu Kim
2025-04-10 13:41 ` David Hildenbrand
2025-04-15 16:00 ` Jonathan Cameron
2025-04-16 4:04 ` Honggyu Kim
2025-04-16 7:37 ` Honggyu Kim
2025-04-16 7:49 ` Rakie Kim
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=20250415164145.00005b6f@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=gourry@gourry.net \
--cc=honggyu.kim@sk.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kernel_team@skhynix.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=rakie.kim@sk.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yunjeong.mun@sk.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.