Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756251AbYFLRN3 (ORCPT ); Thu, 12 Jun 2008 13:13:29 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753449AbYFLRNV (ORCPT ); Thu, 12 Jun 2008 13:13:21 -0400 Received: from netops-testserver-3-out.sgi.com ([192.48.171.28]:60244 "EHLO relay.sgi.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753498AbYFLRNU (ORCPT ); Thu, 12 Jun 2008 13:13:20 -0400 Date: Thu, 12 Jun 2008 10:13:19 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Pekka J Enberg cc: Andrew Morton , Nadia Derbey , Manfred Spraul , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: repeatable slab corruption with LTP msgctl08 In-Reply-To: Message-ID: References: <20080611221324.42270ef2.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 650 Lines: 14 On Thu, 12 Jun 2008, Pekka J Enberg wrote: > I really don't understand how your bufctl chains has so many BUFCTL_END > elements in the first place. It's doesn't look like the memory has been > stomped on (slab->s_mem, for example, is 0xf2906088), so I'd look for a > double kfree() of size 128 somewhere... Looks pretty strange. Could this be rerun with SLAB_DEBUG or with SLUB with full debugging? -- 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/