mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: David Howells <dhowells@redhat.com>
Cc: 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 09:26:23 +0100	[thread overview]
Message-ID: <20090117082623.GB24905@elte.hu> (raw)
In-Reply-To: <16916.1232172471@redhat.com>


* David Howells <dhowells@redhat.com> wrote:

> Ingo Molnar <mingo@elte.hu> wrote:
> 
> > -tip testing found the rather scary looking slab corruption:
> 
> Unfortunately, I'm not in a position to look into this much right 
> now:-(. I'll see if I can find a test machine next week, but if not, 
> it'll be Feb before I can do anything about it.
> 
> That said, what sort of testing were you doing?

It was the regular -tip test cycle/iteration: booting the kernel and 
building the next new (random) kernel on that system, then booting that 
(random) kernel ... etc. The warning occured some time after bootup, so it 
probably triggered during the building of the next kernel. (one kernel 
build takes about 1-2 minutes to finish)

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)

	Ingo

  reply	other threads:[~2009-01-17  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-15 18:16 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 [this message]
2009-01-17 20:33   ` David Howells
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=20090117082623.GB24905@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=eparis@redhat.com \
    --cc=jmorris@namei.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdlemay@epoch.ncsc.mil \
    --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 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®