From: David Howells <dhowells@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: dhowells@redhat.com, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Michael LeMay <mdlemay@epoch.ncsc.mil>,
James Morris <jmorris@namei.org>,
Stephen Smalley <sds@tycho.nsa.gov>,
Paul Moore <paul.moore@hp.com>, Eric Paris <eparis@redhat.com>
Subject: Re: [slab corruption] BUG key_jar: Poison overwritten
Date: Sat, 17 Jan 2009 20:33:22 +0000 [thread overview]
Message-ID: <31147.1232224402@redhat.com> (raw)
In-Reply-To: <20090117082623.GB24905@elte.hu>
Ingo Molnar <mingo@elte.hu> wrote:
> The problem was not reproducible - i tried the same config once more and
> it didnt produce the bug. (this system has no known hardware flukes)
Having thought about it some more, we can't necessarily pin the blame on the
key management code. I think it more likely due to the previous owner of the
page as it's the guard poisoning that got corrupted, not the allocated key
struct. The problem is we don't know who that was. I wonder if it's
practical to store a recent history of page allocs and releases in a circular
buffer.
David
next prev parent reply other threads:[~2009-01-17 20:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-15 18:16 [slab corruption] BUG key_jar: Poison overwritten Ingo Molnar
2009-01-15 20:58 ` Vegard Nossum
2009-01-15 21:01 ` Ingo Molnar
2009-01-15 21:17 ` Vegard Nossum
2009-01-15 21:54 ` Ingo Molnar
2009-01-17 6:07 ` David Howells
2009-01-17 8:26 ` Ingo Molnar
2009-01-17 20:33 ` David Howells [this message]
2009-01-17 21:37 ` Vegard Nossum
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=31147.1232224402@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mdlemay@epoch.ncsc.mil \
--cc=mingo@elte.hu \
--cc=paul.moore@hp.com \
--cc=penberg@cs.helsinki.fi \
--cc=rjw@sisk.pl \
--cc=sds@tycho.nsa.gov \
/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.