On Wed, 30 May 2012, David Mackey wrote: > From: Andi Kleen <ak@xxxxxxxxxxxxxxx> > > slab_node() could access current->mempolicy from interrupt context. > However there's a race condition during exit where the mempolicy > is first freed and then the pointer zeroed. > > Using this from interrupts seems bogus anyways. The interrupt > will interrupt a random process and therefore get a random > mempolicy. Many times, this will be idle's, which noone can change. > > Just disable this here and always use local for slab > from interrupts. I also cleaned up the callers of slab_node a bit > which always passed the same argument. > > I believe the original mempolicy code did that in fact, > so it's likely a regression. > > v2: send version with correct logic > v3: simplify. fix typo. > Reported-by: Arun Sharma <asharma@xxxxxx> > Cc: penberg@xxxxxxxxxx > Cc: cl@xxxxxxxxx > Signed-off-by: Andi Kleen <ak@xxxxxxxxxxxxxxx> > [tdmackey@xxxxxxxxxxx: Rework patch logic and avoid dereference of current > task if in interrupt context.] > Signed-off-by: David Mackey <tdmackey@xxxxxxxxxxx> Acked-by: David Rientjes <rientjes@xxxxxxxxxx> Thanks for following up on this. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>