From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Cc: "Christoph Lameter" <clameter@sgi.com>,
LKML <linux-kernel@vger.kernel.org>,
"Ingo Molnar" <mingo@elte.hu>,
"Mathieu Desnoyers" <mathieu.desnoyers@polymtl.ca>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Torsten Kaiser" <just.for.lkml@googlemail.com>
Subject: Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1
Date: Tue, 19 Feb 2008 09:38:40 +0200 [thread overview]
Message-ID: <84144f020802182338p68d412f6sa9e0f8975344a9c0@mail.gmail.com> (raw)
In-Reply-To: <1203404594.3248.32.camel@ymzhang>
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@linux.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
next prev parent reply other threads:[~2008-02-19 7:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 6:47 Zhang, Yanmin
2008-02-15 16:42 ` Christoph Lameter
2008-02-19 7:03 ` Zhang, Yanmin
2008-02-19 7:38 ` Pekka Enberg [this message]
2008-02-27 22:15 ` Christoph Lameter
2008-02-18 12:59 ` Andrew Morton
2008-02-18 16:52 ` Arjan van de Ven
2008-02-19 3:14 ` Zhang, Yanmin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=84144f020802182338p68d412f6sa9e0f8975344a9c0@mail.gmail.com \
--to=penberg@cs.helsinki.fi \
--cc=clameter@sgi.com \
--cc=just.for.lkml@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yanmin_zhang@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®