Subject: Re: Known prob: MAX_LOCK_DEPTH too low?
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>, Linux-Xfs <linux-xfs@oss.sgi.com>,
       Ingo Molnar <mingo@elte.hu>
In-Reply-To: <4794C7C0.8030207@tlinx.org>
References: <47914FA7.1000807@tlinx.org> <1200918448.6341.5.camel@lappy>
	 <4794C7C0.8030207@tlinx.org>
Content-Type: text/plain
Date: Mon, 21 Jan 2008 18:13:49 +0100
Message-Id: <1200935629.6341.9.camel@lappy>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1299
Lines: 36


On Mon, 2008-01-21 at 08:26 -0800, Linda Walsh wrote:
> Peter Zijlstra wrote:
> > On Fri, 2008-01-18 at 17:17 -0800, Linda Walsh wrote:
> >   
> >> On my x86_64 machine, I got the following message
> >> in log (kern = 2.6.23.14)
> >>
> >> Jan 16 04:08:38 Astara kernel: BUG: MAX_LOCK_DEPTH too low!
> >> Jan 16 04:08:38 Astara kernel: turning off the locking correctness 
> >> validator.
> >>
> >> Have no idea what caused it as I found the message on my console
> >> somewhat after the fact.  The system had been up over 24 hours and
> >> is still running.  System still seems 'fine' (been up 3 days now),
> >> so you can treat this as a "data point".
> >>     
> >
> > Are you perhaps an XFS user?
> >
> >   
> ----
>     Funny you should mention that...  yes.  However, there were no
> other messages that seem to indicate that the message had anything
> to do with XFS.  Nice shot in the dark.

:-), know issue, I guess I'll up the MAX_LOCK_DEPTH for the next
release. I looked at dynamically allocating that stuff, but that gets
awfully painful.


--
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/