[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020802190638i4a364d19o8986a457e76ec187@mail.gmail.com>
Date: Tue, 19 Feb 2008 16:38:50 +0200
From: "Pekka Enberg" <penberg@...helsinki.fi>
To: "Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>
Cc: "Torsten Kaiser" <just.for.lkml@...glemail.com>,
"Ingo Molnar" <mingo@...e.hu>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
"Christoph Lameter" <clameter@....com>
Subject: Re: Linux 2.6.25-rc2
Hi Mathieu,
On Feb 19, 2008 4:02 PM, Mathieu Desnoyers <mathieu.desnoyers@...ymtl.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@...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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists