Messages in this thread | | | Date | Tue, 19 Feb 2008 16:38:50 +0200 | From | "Pekka Enberg" <> | Subject | Re: Linux 2.6.25-rc2 |
| |
Hi Mathieu,
On Feb 19, 2008 4:02 PM, Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> 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 <penberg@cs.helsinki.fi> 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.
| |