xfs
[Top] [All Lists]

Re: [LOCKDEP] xfs: possible recursive locking detected

To: Nathan Scott <nathans@xxxxxxx>
Subject: Re: [LOCKDEP] xfs: possible recursive locking detected
From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Date: Wed, 05 Jul 2006 06:44:50 +0200
Cc: Ingo Molnar <mingo@xxxxxxx>, Alexey Dobriyan <adobriyan@xxxxxxxxx>, Matthew Wilcox <matthew@xxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20060705132328.C1521039@wobbly.melbourne.sgi.com>
References: <20060704004116.GA7612@martell.zuzino.mipt.ru> <20060704011858.GG1605@parisc-linux.org> <20060704112503.H1495869@wobbly.melbourne.sgi.com> <20060704063225.GA2752@elte.hu> <20060704084143.GA12931@elte.hu> <20060704191100.C1497438@wobbly.melbourne.sgi.com> <20060704091247.GA15982@elte.hu> <20060705132328.C1521039@wobbly.melbourne.sgi.com>
Sender: xfs-bounce@xxxxxxxxxxx
On Wed, 2006-07-05 at 13:23 +1000, Nathan Scott wrote:
> On Tue, Jul 04, 2006 at 11:12:47AM +0200, Ingo Molnar wrote:
> > * Nathan Scott <nathans@xxxxxxx> wrote:
> > > That would be good, but it doesn't work for all situations 
> > > unfortunately, and it would loose that debug-kernel sanity checking 
> > > that we have in there which validates ilock/iolock ordering rules.
> > 
> > do you have anything in there that spinlock/mutex debugging or lockdep 
> > does not catch? If yes then i'll add it to the generic lock debugging 
> > code.
> 
> The thing we're catching automatically there is potential ordering
> violations on the XFS inode iolock vs ilock.  

lockdep will catch those just fine.


<Prev in Thread] Current Thread [Next in Thread>