On Thu, 19 Jun 2014, Sasha Levin wrote: > [ 690.770137] ? __this_cpu_preempt_check (lib/smp_processor_id.c:63) > [ 690.770137] __slab_alloc (mm/slub.c:1732 mm/slub.c:2205 mm/slub.c:2369) > [ 690.770137] ? __lock_acquire (kernel/locking/lockdep.c:3189) > [ 690.770137] ? __debug_object_init (lib/debugobjects.c:100 > lib/debugobjects.c:312) > [ 690.770137] kmem_cache_alloc (mm/slub.c:2442 mm/slub.c:2484 mm/slub.c:2489) > [ 690.770137] ? __debug_object_init (lib/debugobjects.c:100 > lib/debugobjects.c:312) > [ 690.770137] ? debug_object_activate (lib/debugobjects.c:439) > [ 690.770137] __debug_object_init (lib/debugobjects.c:100 > lib/debugobjects.c:312) > [ 690.770137] debug_object_init (lib/debugobjects.c:365) > [ 690.770137] rcuhead_fixup_activate (kernel/rcu/update.c:231) > [ 690.770137] debug_object_activate (lib/debugobjects.c:280 > lib/debugobjects.c:439) > [ 690.770137] ? discard_slab (mm/slub.c:1486) > [ 690.770137] __call_rcu (kernel/rcu/rcu.h:76 (discriminator 2) > kernel/rcu/tree.c:2585 (discriminator 2))
__call_rcu does a slab allocation? This means __call_rcu can no longer be used in slab allocators? What happened? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
