From: Randy Dunlap <randy.dunlap@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ken Chen <kenchen@google.com>, linux-mm@kvack.org
Subject: Re: [patch] fix hugetlb page allocation leak
Date: Mon, 23 Jul 2007 19:48:56 -0700 [thread overview]
Message-ID: <20070723194856.40d35666.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20070723172019.376ca936.akpm@linux-foundation.org>
On Mon, 23 Jul 2007 17:20:19 -0700 Andrew Morton wrote:
> On Mon, 23 Jul 2007 17:11:49 -0700
> "Ken Chen" <kenchen@google.com> wrote:
>
> > dequeue_huge_page() has a serious memory leak upon hugetlb page
> > allocation. The for loop continues on allocating hugetlb pages out of
> > all allowable zone, where this function is supposedly only dequeue one
> > and only one pages.
> >
> > Fixed it by breaking out of the for loop once a hugetlb page is found.
> >
> >
> > Signed-off-by: Ken Chen <kenchen@google.com>
Acked-and-tested-by: Randy Dunlap <randy.dunlap@oracle.com>
Thanks.
> > diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> > index f127940..d7ca59d 100644
> > --- a/mm/hugetlb.c
> > +++ b/mm/hugetlb.c
> > @@ -84,6 +84,7 @@ static struct page *dequeue_huge_page(st
> > list_del(&page->lru);
> > free_huge_pages--;
> > free_huge_pages_node[nid]--;
> > + break;
> > }
> > }
> > return page;
>
> that would be due to some idiot merging untested stuff.
well, I should have reported it earlier... :(
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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:[~2007-07-24 2:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 0:11 Ken Chen
2007-07-24 0:20 ` Andrew Morton
2007-07-24 2:48 ` Randy Dunlap [this message]
2007-07-24 17:13 ` Mel Gorman
2007-07-24 15:44 ` Nish Aravamudan
2007-07-24 16:51 ` Andrew Morton
2007-07-24 16:57 ` Nish Aravamudan
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=20070723194856.40d35666.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-mm@kvack.org \
/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