Date: Sat, 17 Jan 2009 09:26:23 +0100
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
Message-ID: <20090117082623.GB24905@elte.hu>
References: <20090115181612.GA27762@elte.hu> <16916.1232172471@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16916.1232172471@redhat.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1128
Lines: 28


* 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/