Hi Mathieu, On Feb 19, 2008 4:02 PM, Mathieu Desnoyers <[EMAIL PROTECTED]> wrote: > > Since this shows mostly with network card drivers, I think the most > > plausible cause would be an IRQ nesting over kmem_cache_alloc_node and > > calling it.
On Feb 19, 2008 4:21 PM, Pekka Enberg <[EMAIL PROTECTED]> wrote: > Yes, this can happen. Are you saying it is not safe to be in the > lockless path when an IRQ triggers? Hmm. The barrier() in slab_free() looks fishy. The comment says it's there to make sure we've retrieved c->freelist before c->page but then it uses a _compiler barrier_ which doesn't affect the CPU and the reads may still be re-ordered... Not sure if that matters here though. -- 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/
