public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: NULL pointer in kmem_cache_alloc with 2.6.25-rc1
Date: Tue, 19 Feb 2008 15:03:14 +0800	[thread overview]
Message-ID: <1203404594.3248.32.camel@ymzhang> (raw)
In-Reply-To: <Pine.LNX.4.64.0802150839180.12023@schroedinger.engr.sgi.com>

On Fri, 2008-02-15 at 08:42 -0800, Christoph Lameter wrote:
> On Fri, 15 Feb 2008, Zhang, Yanmin wrote:
> 
> > On my 16-core tigerton, kernel panic when I ran hackbench process testing. See
> > below log.
> > 
> 
> > 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?
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.

-yanmin



  reply	other threads:[~2008-02-19  7:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15  6:47 NULL pointer in kmem_cache_alloc with 2.6.25-rc1 Zhang, Yanmin
2008-02-15 16:42 ` Christoph Lameter
2008-02-19  7:03   ` Zhang, Yanmin [this message]
2008-02-19  7:38     ` Pekka Enberg
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=1203404594.3248.32.camel@ymzhang \
    --to=yanmin_zhang@linux.intel.com \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    /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