linux-kernel - Re: 2.6.20.3 - 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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 26 Apr 2007 12:17:47 +0200
From:	"Jesper Juhl" <jesper.juhl@...il.com>
To:	"David Chinner" <dgc@....com>
Cc:	linux-kernel@...r.kernel.org, xfs-masters@....sgi.com,
	xfs@....sgi.com, viro@...iv.linux.org.uk
Subject: Re: 2.6.20.3 - possible recursive locking detected - in XFS

On 26/04/07, David Chinner <dgc@....com> wrote:
> On Wed, Apr 25, 2007 at 11:16:57AM +0200, Jesper Juhl wrote:
> >
> > Hi,
> >
> > For your information :
> >
> > Once in a while I see the message below after I've just created a new XFS filesystem, mount it and then start copying data to it.
>
> .....
>
> > =============================================
> > [ INFO: possible recursive locking detected ]
> > 2.6.20.3generic #1
> > ---------------------------------------------
> > xfs_fsr/6117 is trying to acquire lock:
> >  (&(&ip->i_lock)->mr_lock){----}, at: [<f929422d>] xfs_ilock+0x7d/0xa0 [xfs]
> >
> > but task is already holding lock:
> >  (&(&ip->i_lock)->mr_lock){----}, at: [<f929422d>] xfs_ilock+0x7d/0xa0 [xfs]
>
> Known false positive - XFS doesn't have the annotations needed for
> this yet; we've got a patch that will probably make it's way into 6.5.22 that
> should fix most of these issues.
>
Ok. Thanks for the feedback.

-- 
Jesper Juhl <jesper.juhl@...il.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html
-
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/