From: Benny Halevy <bhalevy@panasas.com>
To: Christoph Lameter <clameter@sgi.com>,
Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] SLUB: clear c->freelist in __slab_alloc()/load_freelist:/SlabDebug path
Date: Wed, 14 May 2008 10:54:26 -0700 [thread overview]
Message-ID: <482B2752.2090600@panasas.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805141043200.15374@schroedinger.engr.sgi.com>
On May. 14, 2008, 10:44 -0700, Christoph Lameter <clameter@sgi.com> wrote:
> On Tue, 13 May 2008, Benny Halevy wrote:
>
>>> But for debug pages, we never load c->page->freelist to c->freelist so
>>> it should always be NULL.
>> Hmm, I see. Then it might have got corrupted...
>> I'll keep looking for the root cause.
>
> Correct.
Yeah, I've moved to SLAB and the mem corruption now pops up at a different
place.
>
>>> How did you make SLUB hit the debug path since you have
>>> CONFIG_SLUB_DEBUG_ON disabled?
>
> I guess he passed slub_debug on the kernel command line.
>
I did not.
I probably have misunderstood how the slub debugging infrastructure works
and did not execute the debug path at all.
Thanks for your help!
Benny
next prev parent reply other threads:[~2008-05-14 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 20:32 [PATCH] SLUB: clear c->freelist in __slab_alloc()/load_freelist:/SlabDebug path Benny Halevy
2008-05-13 6:14 ` Pekka Enberg
2008-05-13 18:40 ` Pekka Enberg
2008-05-13 19:34 ` Benny Halevy
2008-05-14 17:44 ` Christoph Lameter
2008-05-14 17:54 ` Benny Halevy [this message]
2008-05-14 17:58 ` Christoph Lameter
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=482B2752.2090600@panasas.com \
--to=bhalevy@panasas.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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