linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: zhong jiang <zhongjiang@huawei.com>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
	hannes@cmpxchg.org, mgorman@techsingularity.net,
	linux-mm@kvack.org
Subject: Re: [PATCH v2] mm: fix the memory leak after collapsing the huge page fails
Date: Wed, 10 May 2017 08:51:20 +0200	[thread overview]
Message-ID: <6810ea54-faed-fcc1-7751-ff91fa3f9d8e@suse.cz> (raw)
In-Reply-To: <5911C9F9.3020802@huawei.com>

On 05/09/2017 03:54 PM, zhong jiang wrote:
> Hi, Vlastimil
> 
> I review the code again. it works well for NUMA. because
> khugepaged_prealloc_page will put_page when *hpage is true.
> 
> the memory leak will still exist in !NUMA. because it ingore
> the put_page. is it right? I miss something.

No, on !NUMA the preallocated and unused new_page is freed by put_page()
at the very end of khugepaged_do_scan().

> Thanks
> zhongjiang
> 
> On 2017/5/9 20:41, Vlastimil Babka wrote:
>> On 05/09/2017 02:20 PM, zhong jiang wrote:
>>> On 2017/5/9 19:34, Vlastimil Babka wrote:
>>>> On 05/09/2017 12:55 PM, zhongjiang wrote:
>>>>> From: zhong jiang <zhongjiang@huawei.com>
>>>>>
>>>>> Current, when we prepare a huge page to collapse, due to some
>>>>> reasons, it can fail to collapse. At the moment, we should
>>>>> release the preallocate huge page.
>>>>>
>>>>> Signed-off-by: zhong jiang <zhongjiang@huawei.com>
>>>> Hmm, scratch that, there's no memory leak. The pointer to new_page is
>>>> stored in *hpage, and put_page() is called all the way up in
>>>> khugepaged_do_scan().
>>>  I see. I miss it. but why the new_page need to be release all the way.
>> AFAIK to support preallocation and reusal of preallocated page for
>> collapse attempt in different pmd. It only works for !NUMA so it's
>> likely not worth all the trouble and complicated code, so I wouldn't be
>> opposed to simplifying this.
>>
>>>  I do not see the count increment when scan success. it save the memory,
>>>  only when page fault happen.
>> I don't understand what you mean here?
>>
>>>  Thanks
>>>  zhongjiang
>>>>> ---
>>>>>  mm/khugepaged.c | 4 ++++
>>>>>  1 file changed, 4 insertions(+)
>>>>>
>>>>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>>>>> index 7cb9c88..586b1f1 100644
>>>>> --- a/mm/khugepaged.c
>>>>> +++ b/mm/khugepaged.c
>>>>> @@ -1082,6 +1082,8 @@ static void collapse_huge_page(struct mm_struct *mm,
>>>>>  	up_write(&mm->mmap_sem);
>>>>>  out_nolock:
>>>>>  	trace_mm_collapse_huge_page(mm, isolated, result);
>>>>> +	if (page != NULL && result != SCAN_SUCCEED)
>>>>> +		put_page(new_page);
>>>>>  	return;
>>>>>  out:
>>>>>  	mem_cgroup_cancel_charge(new_page, memcg, true);
>>>>> @@ -1555,6 +1557,8 @@ static void collapse_shmem(struct mm_struct *mm,
>>>>>  	}
>>>>>  out:
>>>>>  	VM_BUG_ON(!list_empty(&pagelist));
>>>>> +	if (page != NULL && result != SCAN_SUCCEED)
>>>>> +		put_page(new_page);
>>>>>  	/* TODO: tracepoints */
>>>>>  }
>>>>>  
>>>>>
>>>> .
>>>>
>>>
>>
>> .
>>
> 
> 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2017-05-10  6:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 10:55 zhongjiang
2017-05-09 11:34 ` Vlastimil Babka
2017-05-09 12:20   ` zhong jiang
2017-05-09 12:41     ` Vlastimil Babka
2017-05-09 13:31       ` zhong jiang
2017-05-09 13:46         ` Vlastimil Babka
2017-05-09 13:56           ` zhong jiang
2017-05-09 13:54       ` zhong jiang
2017-05-10  6:51         ` Vlastimil Babka [this message]
2017-05-10  7:59           ` zhong jiang

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=6810ea54-faed-fcc1-7751-ff91fa3f9d8e@suse.cz \
    --to=vbabka@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=hannes@cmpxchg.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=zhongjiang@huawei.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