linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: liuye <liuye@kylinos.cn>
Cc: Qi Zheng <zhengqi.arch@bytedance.com>,
	akpm@linux-foundation.org, david@fromorbit.com,
	roman.gushchin@linux.dev, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/shrinker_debug: Fix possible memory leak in shrinker_debugfs_rename function.
Date: Wed, 5 Mar 2025 14:46:02 +0800	[thread overview]
Message-ID: <451E5C9A-F7FB-41DD-B760-25E4883B0861@linux.dev> (raw)
In-Reply-To: <875d80ee-d99a-4580-8648-36adb1e8591c@kylinos.cn>



> On Mar 5, 2025, at 14:10, liuye <liuye@kylinos.cn> wrote:
> 
> 
> 在 2025/3/5 11:26, Qi Zheng 写道:
>> 
>> 
>> On 3/5/25 11:17 AM, Muchun Song wrote:
>>> 
>>> 
>>>> On Mar 5, 2025, at 10:01, Liu Ye <liuye@kylinos.cn> wrote: 
>>>> 
>>>> After calling debugfs_change_name function, the return value should be 
>>>> checked and the old name restored. If debugfs_change_name fails, the new 
>>>> name memory should be freed.
>>> 
>>> Seems it is not a big problem, no memory leak at least. The effect is that 
>>> the shrinker->name is not consistent with the name displayed in debugfs. 
>>> Right? But the improvement LGTM. So:
>> 
>> Right, so the subject needs to be changed. 
>> 
>> Maybe: 
>> 
>> mm: shrinker: fix name consistency issue in shrinker_debugfs_rename()
>> 
>> ?
>  I will send a new patch using this subject later.

Please update the commit message as well to include the effect.

> And add  Reviewed-by:Qi Zheng <zhengqi.arch@bytedance.com> ?
> 
>> 
>> BTW, it seems that the callers of shrinker_debugfs_rename() did not 
>> process the return value of the function?
> 
> Yes,  At the same time, I also found that many positions using 
> debugfs_change_name did not determine the return value.
> 
>> 
>>> 
>>> Reviewed-by: Muchun Song <muchun.song@linux.dev> 
>>> 
>>> Thanks.
> Thanks.
>>> 
>>>> 
>>>> Signed-off-by: Liu Ye <liuye@kylinos.cn> 
>>>> --- 
>>>> mm/shrinker_debug.c | 8 ++++++-- 
>>>> 1 file changed, 6 insertions(+), 2 deletions(-) 
>>>> 
>>>> diff --git a/mm/shrinker_debug.c b/mm/shrinker_debug.c 
>>>> index 794bd433cce0..20eaee3e97f7 100644 
>>>> --- a/mm/shrinker_debug.c 
>>>> +++ b/mm/shrinker_debug.c 
>>>> @@ -214,10 +214,14 @@ int shrinker_debugfs_rename(struct shrinker *shrinker, const char *fmt, ...) 
>>>> ret = debugfs_change_name(shrinker->debugfs_entry, "%s-%d", 
>>>> shrinker->name, shrinker->debugfs_id); 
>>>> 
>>>> +     if (ret) { 
>>>> +         shrinker->name = old; 
>>>> +         kfree_const(new); 
>>>> +     } else { 
>>>> +         kfree_const(old); 
>>>> +     } 
>>>>     mutex_unlock(&shrinker_mutex); 
>>>> 
>>>> -     kfree_const(old); 
>>>> - 
>>>>     return ret; 
>>>> } 
>>>> EXPORT_SYMBOL(shrinker_debugfs_rename); 
>>>> -- 
>>>> 2.25.1 
>>>> 
>>> 
>> 



      parent reply	other threads:[~2025-03-05 18:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  2:01 Liu Ye
2025-03-05  3:17 ` Muchun Song
2025-03-05  3:26   ` Qi Zheng
     [not found]     ` <875d80ee-d99a-4580-8648-36adb1e8591c@kylinos.cn>
2025-03-05  6:46       ` Muchun Song [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=451E5C9A-F7FB-41DD-B760-25E4883B0861@linux.dev \
    --to=muchun.song@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    --cc=roman.gushchin@linux.dev \
    --cc=zhengqi.arch@bytedance.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