From: Jan Niehusmann <jan@gondor.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Andrew Morton <akpm@osdl.org>, Dave Jones <davej@redhat.com>,
Paul Fulghum <paulkf@microgate.com>,
linux-kernel@vger.kernel.org
Subject: Re: yet more slab corruption.
Date: Tue, 4 Apr 2006 16:21:43 +0200 [thread overview]
Message-ID: <20060404142143.GA5159@knautsch.gondor.com> (raw)
In-Reply-To: <200604041544.01656.agruen@suse.de>
On Tue, Apr 04, 2006 at 03:44:01PM +0200, Andreas Gruenbacher wrote:
> We have two similar bug reports to
> https://bugzilla.redhat.com/bugzilla/184310, slab corruption in an object
> freed by release_mem:
>
> https://bugzilla.novell.com/151111 (i386)
> https://bugzilla.novell.com/154601 (x86_64)
>
> So this bug seems to trigger on different architectures, and with different
> hardware.
I also got a few of these, just reported in a different thread,
see http://lkml.org/lkml/2006/4/4/86 for details.
Jan
prev parent reply other threads:[~2006-04-04 14:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 23:59 yet more slab corruption Dave Jones
2006-03-08 7:14 ` Andrew Morton
2006-04-04 13:44 ` Andreas Gruenbacher
2006-04-04 14:21 ` Jan Niehusmann [this message]
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=20060404142143.GA5159@knautsch.gondor.com \
--to=jan@gondor.com \
--cc=agruen@suse.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulkf@microgate.com \
/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