From: Andrew Morton <akpm@linux-foundation.org>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Ken Chen <kenchen@google.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-mm@kvack.org
Subject: Re: [patch] fix hugetlb page allocation leak
Date: Tue, 24 Jul 2007 09:51:46 -0700 [thread overview]
Message-ID: <20070724095146.bd9fad5e.akpm@linux-foundation.org> (raw)
In-Reply-To: <29495f1d0707240844k2f08d210id76bd53c63cc9cd1@mail.gmail.com>
On Tue, 24 Jul 2007 08:44:01 -0700 "Nish Aravamudan" <nish.aravamudan@gmail.com> wrote:
> On 7/23/07, Andrew Morton <akpm@linux-foundation.org> 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>
> > >
> > > 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.
>
> This would be due to 3abf7afd406866a84276d3ed04f4edf6070c9cb5 right?
yep.
> Now, I wrote 31a5c6e4f25704f51f9a1373f0784034306d4cf1 which I'm
> assuming introduced this compile warning. But on my box, I see no such
> warning. I would like to think I wouldn't have submitted a patch that
> introduce the warning, even if it was trivial like that one. Which
> compiler were you using, Andrew?
I expect it was gcc-4.1.0.
But most gcc's will get confused over that code sequence.
> And if anything, I think it's a gcc bug, no? I don't see how nid could
> be used if it wasn't initialized by the zone_to_nid() call. Shouldn't
> this have got one of those uninitialized_var() things? I guess the
> code reorder (if it had included the 'break') would be just as good,
> but I'm not sure.
Yes, gcc gets things wrong.
--
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 16:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-24 0:11 [patch] fix hugetlb page allocation leak Ken Chen
2007-07-24 0:20 ` Andrew Morton
2007-07-24 2:48 ` Randy Dunlap
2007-07-24 17:13 ` Mel Gorman
2007-07-24 15:44 ` Nish Aravamudan
2007-07-24 16:51 ` Andrew Morton [this message]
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=20070724095146.bd9fad5e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kenchen@google.com \
--cc=linux-mm@kvack.org \
--cc=nish.aravamudan@gmail.com \
--cc=randy.dunlap@oracle.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.