From: Andrew Morton <akpm@osdl.org>
To: Dave Jones <davej@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: yet more slab corruption.
Date: Tue, 7 Mar 2006 23:14:14 -0800 [thread overview]
Message-ID: <20060307231414.34c3b3a4.akpm@osdl.org> (raw)
In-Reply-To: <20060307235940.GA16843@redhat.com>
Dave Jones <davej@redhat.com> wrote:
>
> Garg. Is there no end to these ?
> That kernel is based off 2.6.16rc5-git8
>
> This brings the current count up to 8 different patterns filed
> against our 2.6.16rc tree in Fedora bugzilla.
> (One of them doesn't count as it's against the out-of-tree bcm43xx driver).
>
A use-after-free on size-2048. We wrote -1L and 0L apparently 0x6b8 bytes
into the object. That's an awfully large offset for tty_struct - off the
end. Sometimes the buffer was used as skb data too.
Unless it was a DMA scribble, CONFIG_DEBUG_PAGEALLOC should catch this.
next prev parent reply other threads:[~2006-03-08 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 23:59 Dave Jones
2006-03-08 7:14 ` Andrew Morton [this message]
2006-04-04 13:44 ` Andreas Gruenbacher
2006-04-04 14:21 ` Jan Niehusmann
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=20060307231414.34c3b3a4.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davej@redhat.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
all inboxes | Powered by JetHome®