[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <84144f020802182338p68d412f6sa9e0f8975344a9c0@mail.gmail.com>
Date: Tue, 19 Feb 2008 09:38:40 +0200
From: "Pekka Enberg" <penberg@...helsinki.fi>
To: "Zhang, Yanmin" <yanmin_zhang@...ux.intel.com>
Cc: "Christoph Lameter" <clameter@....com>,
LKML <linux-kernel@...r.kernel.org>,
"Ingo Molnar" <mingo@...e.hu>,
"Mathieu Desnoyers" <mathieu.desnoyers@...ymtl.ca>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
"Torsten Kaiser" <just.for.lkml@...glemail.com>
Subject: Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1
Hi Yanmin,
> On Fri, 2008-02-15 at 08:42 -0800, Christoph Lameter wrote:
> > > Kernel panic at line 1637 in file mm/slub.c because object=c->freelist=NULL.
> >
> > Hmmmm. freelist should never be NULL. Could you rerun the test and boot with
> > slub_debug to make sure that there is no memory corruption?
On Feb 19, 2008 9:03 AM, Zhang, Yanmin <yanmin_zhang@...ux.intel.com> wrote:
> 1) Without slub_debug option, sometime I could trigger it, sometimes not.
> 2) With slub_debug option, or just enable debug for slab skbuff_fclone_cache
> and skbuff_head_cache, I couldn't trigger it.
>
> I will do more testing and investigation, as the bug also exists in 2.6.25-rc2.
Could you please try Ingo's patch: http://lkml.org/lkml/2008/2/19/13
Looks like there are some problems with SLUB_FASTPATH.
Pekka
--
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