From: Li Zhong <zhong@linux.vnet.ibm.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: linux-mm <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH]mm: fix potential infinite loop in dissolve_free_huge_pages()
Date: Mon, 28 Jul 2014 09:28:01 +0800 [thread overview]
Message-ID: <1406510881.2941.2.camel@TP-T420> (raw)
In-Reply-To: <20140724124511.GA14379@nhori>
On Thu, 2014-07-24 at 08:45 -0400, Naoya Horiguchi wrote:
> Hi Zhong,
>
> On Thu, Jul 24, 2014 at 05:36:25PM +0800, Li Zhong wrote:
> > It is possible for some platforms, such as powerpc to set HPAGE_SHIFT to
> > 0 to indicate huge pages not supported.
> >
> > When this is the case, hugetlbfs could be disabled during boot time:
> > hugetlbfs: disabling because there are no supported hugepage sizes
> >
> > Then in dissolve_free_huge_pages(), order is kept maximum (64 for
> > 64bits), and the for loop below won't end:
> > for (pfn = start_pfn; pfn < end_pfn; pfn += 1 << order)
>
> At first I wonder that why could dissolve_free_huge_pages() is called
> if the platform doesn't support hugetlbfs. But I found that the function
> is called by memory hotplug code without checking hugepage support.
>
> So it looks to me straightforward and self-descriptive to check
> hugepage_supported() just before calling dissolve_free_huge_pages().
Hi, Naoya,
Thank you for the review and suggestion.
I'll send a updated version.
Thanks, Zhong
>
> Thanks,
> Naoya Horiguchi
>
> > The fix below returns directly if the order isn't set to a correct
> > value.
> >
> > Signed-off-by: Li Zhong <zhong@linux.vnet.ibm.com>
> > ---
> > mm/hugetlb.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> >
> > diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> > index 2024bbd..a950817 100644
> > --- a/mm/hugetlb.c
> > +++ b/mm/hugetlb.c
> > @@ -1093,6 +1093,10 @@ void dissolve_free_huge_pages(unsigned long start_pfn, unsigned long end_pfn)
> > for_each_hstate(h)
> > if (order > huge_page_order(h))
> > order = huge_page_order(h);
> > +
> > + if (order == 8 * sizeof(void *))
> > + return;
> > +
> > VM_BUG_ON(!IS_ALIGNED(start_pfn, 1 << order));
> > for (pfn = start_pfn; pfn < end_pfn; pfn += 1 << order)
> > dissolve_free_huge_page(pfn_to_page(pfn));
> >
> >
> > --
> > 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>
> >
>
--
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:[~2014-07-28 1:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 9:36 [RFC PATCH]mm: fix potential infinite loop in dissolve_free_huge_pages() Li Zhong
2014-07-24 12:45 ` Naoya Horiguchi
2014-07-28 1:28 ` Li Zhong [this message]
2014-07-28 2:20 ` [PATCH v2]mm: " Li Zhong
2014-07-28 14:33 ` Naoya Horiguchi
2014-07-30 1:09 ` [patch] mm: fix potential infinite loop in dissolve_free_huge_pages() fix David Rientjes
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=1406510881.2941.2.camel@TP-T420 \
--to=zhong@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.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).