xfs
[Top] [All Lists]

Re: [LOCKDEP] xfs: possible recursive locking detected

To: Alexey Dobriyan <adobriyan@xxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Matthew Wilcox <matthew@xxxxxx>
Subject: Re: [LOCKDEP] xfs: possible recursive locking detected
From: Nathan Scott <nathans@xxxxxxx>
Date: Tue, 4 Jul 2006 11:25:03 +1000
Cc: linux-fsdevel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20060704011858.GG1605@xxxxxxxxxxxxxxxx>; from matthew@xxxxxx on Mon, Jul 03, 2006 at 07:18:58PM -0600
References: <20060704004116.GA7612@xxxxxxxxxxxxxxxxxxxxxx> <20060704011858.GG1605@xxxxxxxxxxxxxxxx>
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Mon, Jul 03, 2006 at 07:18:58PM -0600, Matthew Wilcox wrote:
> On Tue, Jul 04, 2006 at 04:41:16AM +0400, Alexey Dobriyan wrote:
> > 2.6.17-912b2539e1e062cec73e2e61448e507f7719bd08
> > 
> > While trying to remove 2 small files, 2 empty dirs and 1 empty dir on
> > xfs partition
> 
> Probably spurious.  xfs_ilock can be called on both the parent and child,
> which wouldn't be a deadlock.

Hmm... they'd be different inodes though, so different lock addresses
in memory - is lockdep taking that into account?  Would we need to go
annotate xfs_ilock somehow to give better hints to the lockdep code?

thanks.

-- 
Nathan


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