On 06/19/2014 04:29 PM, Paul E. McKenney wrote: > rcu: Provide call_rcu_alloc() and call_rcu_sched_alloc() to avoid recursion > > The sl*b allocators use call_rcu() to manage object lifetimes, but > call_rcu() can use debug-objects, which in turn invokes the sl*b > allocators. These allocators are not prepared for this sort of > recursion, which can result in failures. > > This commit therefore creates call_rcu_alloc() and call_rcu_sched_alloc(), > which act as their call_rcu() and call_rcu_sched() counterparts, but > which avoid invoking debug-objects. These new API members are intended > only for use by the sl*b allocators, and this commit makes the sl*b > allocators use call_rcu_alloc(). Why call_rcu_sched_alloc()? Because > in CONFIG_PREEMPT=n kernels, call_rcu() maps to call_rcu_sched(), so > therefore call_rcu_alloc() must map to call_rcu_sched_alloc(). > > Reported-by: Sasha Levin <sasha.le...@oracle.com> > Set-straight-by: Thomas Gleixner <t...@linutronix.de> > Signed-off-by: Paul E. McKenney <paul...@linux.vnet.ibm.com>
Paul, what is this patch based on? It won't apply cleanly on -next or Linus's tree. Thanks, Sasha -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
