linux-kernel - Re: xfs_ilock: possible recursive locking detected

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20070508023239.GB32602149@melbourne.sgi.com>
Date:	Tue, 8 May 2007 12:32:39 +1000
From:	David Chinner <dgc@....com>
To:	Simon Arlott <simon@...e.lp0.eu>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	xfs@....sgi.com, xfs-masters@....sgi.com
Subject: Re: xfs_ilock: possible recursive locking detected

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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/