Re: [BUG] set_mempolicy(MPOL_INTERLEAV) cause kernel panic

[David Rientjes]

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.

> Could you teach me a pointer for Lee's observation ?
> 

http://marc.info/?l=linux-kernel&m=124767909310293
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/