From: Dave Jones <davej@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: frequent slab corruption (since a long time)
Date: Wed, 2 Aug 2006 00:22:00 -0400 [thread overview]
Message-ID: <20060802042200.GA30216@redhat.com> (raw)
In-Reply-To: <p73fygfzu2v.fsf@verdi.suse.de>
On Wed, Aug 02, 2006 at 05:37:28AM +0200, Andi Kleen wrote:
> Dave Jones <davej@redhat.com> writes:
>
> > Every so often, I see a slab corruption bug reported against
> > the Fedora kernels (going back as far as 2.6.11), and it's
> > still plagueing us.
> >
> > It seems to have turned up in a number of different scenarios,
> > which makes it all the more complicated, but the footprint is
> > always the same. We write ffffffff00000000 to freed memory.
>
> DEBUG_PAGEALLOC + a small slab patch to force the 2k slab to be
> only a single object per page (so that a kfree() immediately
> triggers an unmap) would catch it I guess.
Problem with that approach is that DEBUG_PAGEALLOC makes things
so damned slow that it's pretty much unusable, and this bug
doesn't seem to want to repeat itself to order, so I doubt
many people would put up with the slowdown long enough to chase it down.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-08-02 4:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-02 2:16 frequent slab corruption (since a long time) Dave Jones
2006-08-02 2:34 ` Roland Dreier
2006-08-02 3:37 ` Andi Kleen
2006-08-02 4:22 ` Dave Jones [this message]
2006-08-02 4:35 ` Andi Kleen
2006-08-02 4:46 ` Dave Jones
2006-08-02 5:05 ` David Miller
2006-08-02 5:31 ` David Miller
2006-08-02 22:23 ` Dave Jones
2006-08-02 22:49 ` David Miller
2006-08-03 17:40 ` Alan Cox
2006-08-03 17:56 ` Dave Jones
2006-08-03 20:48 ` Alan Cox
2006-08-02 23:14 ` Alan Cox
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=20060802042200.GA30216@redhat.com \
--to=davej@redhat.com \
--cc=ak@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.