From: Vlastimil Babka <vbabka@suse.cz>
To: zhongjiang <zhongjiang@huawei.com>, akpm@linux-foundation.org
Cc: 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: Tue, 9 May 2017 13:34:10 +0200 [thread overview]
Message-ID: <442638e9-d6db-2f1c-e260-9290d7524f1d@suse.cz> (raw)
In-Reply-To: <1494327305-835-1-git-send-email-zhongjiang@huawei.com>
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().
> ---
> 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>
next prev parent reply other threads:[~2017-05-09 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 10:55 [PATCH v2] mm: fix the memory leak after collapsing the huge page fails zhongjiang
2017-05-09 11:34 ` Vlastimil Babka [this message]
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
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=442638e9-d6db-2f1c-e260-9290d7524f1d@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;
as well as URLs for NNTP newsgroup(s).