Re: [LOCKDEP] xfs: possible recursive locking detected

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux