Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757921AbZGGPeR (ORCPT ); Tue, 7 Jul 2009 11:34:17 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756092AbZGGPeD (ORCPT ); Tue, 7 Jul 2009 11:34:03 -0400 Received: from viefep15-int.chello.at ([62.179.121.35]:26592 "EHLO viefep15-int.chello.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755448AbZGGPeB (ORCPT ); Tue, 7 Jul 2009 11:34:01 -0400 X-SourceIP: 213.93.53.227 Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES From: Peter Zijlstra To: Joao Correia Cc: LKML , Amerigo Wang In-Reply-To: References: Content-Type: text/plain Date: Tue, 07 Jul 2009 17:33:56 +0200 Message-Id: <1246980836.9777.5.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 866 Lines: 21 On Tue, 2009-07-07 at 16:25 +0100, Joao Correia wrote: > (Applies to current Linus tree, as of 2.6.31-rc2) > > As it stands now, the limit is too low and is being hit by false > positives. Increasing its value will allow for more room to work with. > > This was suggested by Ingo Molnar > (http://article.gmane.org/gmane.linux.kernel/852005) but never > submitted as a patch, to the best of my knowledge. Right, we found a bug in the dma-debug code that generated tons of classes where only 1 was needed, which in turn generated tons of chains and stack entries. But that got merged, but you're seeing more of this? -- 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/