From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
miaox@cn.fujitsu.com, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Christoph Lameter <cl@linux-foundation.org>,
Paul Menage <menage@google.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
y-goto@jp.fujitsu.com, Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic
Date: Tue, 28 Jul 2009 10:24:11 +0900 [thread overview]
Message-ID: <20090728102411.2a18c2e3.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090728101157.9465b2e5.kamezawa.hiroyu@jp.fujitsu.com>
On Tue, 28 Jul 2009 10:11:57 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> On Mon, 27 Jul 2009 18:02:50 -0700 (PDT)
> David Rientjes <rientjes@google.com> wrote:
>
> > On Tue, 28 Jul 2009, KAMEZAWA Hiroyuki wrote:
> >
> > > > The problem originally reported here doesn't appear to have anything to do
> > > > with hotplug, it looks like it is the result of Lee's observation that
> > > > ia64 defaults top_cpuset's mems to N_POSSIBLE, which _should_ have been
> > > > updated by cpuset_init_smp().
> > > cpuset_init_smp() just updates cpuset's mask.
> > > init's task->mems_allowed is intizialized independently from cpuset's mask.
> > >
> >
> > Presumably the bug is that N_HIGH_MEMORY is not a subset of N_ONLINE at
> > this point on ia64.
> >
> N_HIGH_MEMORY is must be subset of N_ONLINE, at the any moment. Hmm,
> I'll look into what happens in ia64 world.
>
At quick look, N_HIGH_MEMORY is set here while init. (I ignore hoplug now.)
== before init==
60 #ifndef CONFIG_NUMA
61 [N_NORMAL_MEMORY] = { { [0] = 1UL } },
62 #ifdef CONFIG_HIGHMEM
63 [N_HIGH_MEMORY] = { { [0] = 1UL } },
64 #endif
==
3860 static unsigned long __init early_calculate_totalpages(void)
3861 {
....
3869 if (pages)
3870 node_set_state(early_node_map[i].nid, N_HIGH_MEMORY);
3871 }
==
4041 void __init free_area_init_nodes(unsigned long *max_zone_pfn)
4042 {
4105 if (pgdat->node_present_pages)
4106 node_set_state(nid, N_HIGH_MEMORY);
==
All of them are done while mem_init(). Then if N_HIGH_MEMORY is not correct at
kernel_init(). It's bug.
I think what Lee and Miao pointed out is just a hotplug problem.
Ok, I'll try some patch but it'll take some hours.
Thanks,
-Kame
--
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:[~2009-07-28 1:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 9:48 KOSAKI Motohiro
2009-07-15 17:31 ` Lee Schermerhorn
2009-07-16 1:00 ` KOSAKI Motohiro
2009-07-16 20:05 ` David Rientjes
2009-07-17 0:04 ` KOSAKI Motohiro
2009-07-17 0:57 ` KAMEZAWA Hiroyuki
2009-07-17 2:07 ` KOSAKI Motohiro
2009-07-17 2:39 ` KAMEZAWA Hiroyuki
2009-07-17 9:09 ` David Rientjes
2009-07-17 9:01 ` David Rientjes
2009-07-24 22:51 ` David Rientjes
2009-07-24 23:09 ` Andrew Morton
2009-07-25 1:33 ` KAMEZAWA Hiroyuki
2009-07-25 2:35 ` KAMEZAWA Hiroyuki
2009-07-25 3:15 ` KAMEZAWA Hiroyuki
2009-07-25 13:21 ` KOSAKI Motohiro
2009-07-25 14:40 ` KAMEZAWA Hiroyuki
2009-07-27 18:00 ` David Rientjes
2009-07-27 17:55 ` David Rientjes
2009-07-27 23:58 ` KAMEZAWA Hiroyuki
2009-07-28 0:14 ` David Rientjes
2009-07-28 0:25 ` KAMEZAWA Hiroyuki
2009-07-28 0:38 ` David Rientjes
2009-07-28 0:54 ` KAMEZAWA Hiroyuki
2009-07-28 1:02 ` David Rientjes
2009-07-28 1:11 ` KAMEZAWA Hiroyuki
2009-07-28 1:24 ` KAMEZAWA Hiroyuki [this message]
2009-07-28 7:18 ` [BUGFIX] set_mempolicy(MPOL_INTERLEAV) N_HIGH_MEMORY aware KAMEZAWA Hiroyuki
2009-07-28 8:52 ` Andi Kleen
2009-07-28 10:04 ` KAMEZAWA Hiroyuki
2009-07-29 20:16 ` Andrew Morton
2009-07-30 0:06 ` KAMEZAWA Hiroyuki
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=20090728102411.2a18c2e3.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=miaox@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=y-goto@jp.fujitsu.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