From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Xishi Qiu <qiuxishi@huawei.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
Laura Abbott <lauraa@codeaurora.org>,
"zhuhui@xiaomi.com" <zhuhui@xiaomi.com>,
"wangxq10@lzu.edu.cn" <wangxq10@lzu.edu.cn>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: fix invalid node in alloc_migrate_target()
Date: Wed, 30 Mar 2016 01:13:10 +0000 [thread overview]
Message-ID: <20160330011308.GA12660@hori1.linux.bs1.fc.nec.co.jp> (raw)
In-Reply-To: <56FA741F.7010705@suse.cz>
On Tue, Mar 29, 2016 at 02:25:03PM +0200, Vlastimil Babka wrote:
> On 03/25/2016 07:56 AM, Xishi Qiu wrote:
> >It is incorrect to use next_node to find a target node, it will
> >return MAX_NUMNODES or invalid node. This will lead to crash in
> >buddy system allocation.
>
> One possible place of crash is:
> alloc_huge_page_node()
> dequeue_huge_page_node()
> [accesses h->hugepage_freelists[nid] with size MAX_NUMANODES]
>
> >Signed-off-by: Xishi Qiu <qiuxishi@huawei.com>
>
> Fixes: c8721bbbdd36 ("mm: memory-hotplug: enable memory hotplug to handle
> hugepage")
> Cc: stable
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
Thanks everyone for finding/fixing the bug!
Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
> >---
> > mm/page_isolation.c | 8 ++++----
> > 1 file changed, 4 insertions(+), 4 deletions(-)
> >
> >diff --git a/mm/page_isolation.c b/mm/page_isolation.c
> >index 92c4c36..31555b6 100644
> >--- a/mm/page_isolation.c
> >+++ b/mm/page_isolation.c
> >@@ -289,11 +289,11 @@ struct page *alloc_migrate_target(struct page *page, unsigned long private,
> > * now as a simple work-around, we use the next node for destination.
> > */
> > if (PageHuge(page)) {
> >- nodemask_t src = nodemask_of_node(page_to_nid(page));
> >- nodemask_t dst;
> >- nodes_complement(dst, src);
> >+ int node = next_online_node(page_to_nid(page));
> >+ if (node == MAX_NUMNODES)
> >+ node = first_online_node;
> > return alloc_huge_page_node(page_hstate(compound_head(page)),
> >- next_node(page_to_nid(page), dst));
> >+ node);
> > }
> >
> > if (PageHighMem(page))
> >
>
--
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>
prev parent reply other threads:[~2016-03-30 1:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-25 6:56 Xishi Qiu
2016-03-25 19:22 ` Andrew Morton
2016-03-26 5:31 ` Xishi Qiu
2016-03-29 9:52 ` Vlastimil Babka
2016-03-29 10:06 ` Vlastimil Babka
2016-03-29 10:37 ` Xishi Qiu
2016-03-29 12:21 ` Vlastimil Babka
2016-03-29 13:06 ` Vlastimil Babka
2016-03-31 13:13 ` Vlastimil Babka
2016-03-31 21:01 ` Andrew Morton
2016-04-01 8:42 ` Vlastimil Babka
2016-03-29 15:52 ` Michal Hocko
2016-03-29 12:25 ` Vlastimil Babka
2016-03-30 1:13 ` Naoya Horiguchi [this message]
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=20160330011308.GA12660@hori1.linux.bs1.fc.nec.co.jp \
--to=n-horiguchi@ah.jp.nec.com \
--cc=akpm@linux-foundation.org \
--cc=js1304@gmail.com \
--cc=lauraa@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@huawei.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=wangxq10@lzu.edu.cn \
--cc=zhuhui@xiaomi.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