On Sun, May 06, 2007 at 11:44:45PM +0100, Simon Arlott wrote:
> [ 119.948000] =============================================
> [ 119.948000] [ INFO: possible recursive locking detected ]
> [ 119.948000] 2.6.21-git #185
> [ 119.948000] ---------------------------------------------
> [ 119.948000] cc1/6496 is trying to acquire lock:
> [ 119.948000] (&(&ip->i_lock)->mr_lock){----}, at: [<b025d230>]
> xfs_ilock+0x60/0xb0
> [ 119.948000]
> [ 119.948000] but task is already holding lock:
> [ 119.948000] (&(&ip->i_lock)->mr_lock){----}, at: [<b025d230>]
> xfs_ilock+0x60/0xb0
> [ 119.948000]
Known false positive. There shoul dbe a git update for Linus in the
next couple of days that has the lockdep annotations needed to prevent
these false positives from coming up....
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
