Fwd: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES

[Joao Correia]

(clumsy fingers part 2, forwarding to the list)


---------- Forwarded message ----------
From: Joao Correia <joaomiguelcorreia@xxxxxxxxx>
Date: Tue, Jul 7, 2009 at 4:38 PM
Subject: Re: [PATCH 1/3] Increase lockdep limits: MAX_STACK_TRACE_ENTRIES
To: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>


Yes. Anything 2.6.31 forward triggers this immediatly during init
process, at random places.

Joao Correia

On Tue, Jul 7, 2009 at 4:33 PM, Peter Zijlstra<a.p.zijlstra@xxxxxxxxx> wrote:
> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/