From: Christoph Lameter <clameter@sgi.com>
To: Pekka J Enberg <penberg@cs.helsinki.fi>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nadia Derbey <Nadia.Derbey@bull.net>,
Manfred Spraul <manfred@colorfullife.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: repeatable slab corruption with LTP msgctl08
Date: Thu, 12 Jun 2008 10:13:19 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0806121011320.30597@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0806121332130.11556@sbz-30.cs.Helsinki.FI>
On Thu, 12 Jun 2008, Pekka J Enberg wrote:
> I really don't understand how your bufctl chains has so many BUFCTL_END
> elements in the first place. It's doesn't look like the memory has been
> stomped on (slab->s_mem, for example, is 0xf2906088), so I'd look for a
> double kfree() of size 128 somewhere...
Looks pretty strange. Could this be rerun with SLAB_DEBUG or with SLUB
with full debugging?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-06-12 17:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 5:13 Andrew Morton
2008-06-12 6:34 ` Andrew Morton
2008-06-12 8:02 ` Andrew Morton
2008-06-12 8:15 ` Andrew Morton
2008-06-12 8:16 ` Andrew Morton
2008-06-12 8:35 ` Andi Kleen
2008-06-12 9:08 ` Andrew Morton
2008-06-12 10:24 ` Andrew Morton
2008-06-12 10:41 ` Andi Kleen
2008-06-12 10:35 ` Pekka J Enberg
2008-06-12 17:13 ` Christoph Lameter [this message]
2008-06-12 18:33 ` Manfred Spraul
2008-06-12 18:41 ` Andrew Morton
2008-06-12 19:09 ` Manfred Spraul
2008-06-12 19:20 ` Andrew Morton
2008-06-12 19:27 ` Pekka Enberg
2008-06-13 7:03 ` Nadia Derbey
2008-06-13 8:33 ` Nadia Derbey
2008-06-13 8:42 ` Andrew Morton
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=Pine.LNX.4.64.0806121011320.30597@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=Nadia.Derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--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