public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Chinner <dgc@sgi.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: linux-kernel@vger.kernel.org, xfs-masters@oss.sgi.com,
	xfs@oss.sgi.com, viro@zeniv.linux.org.uk
Subject: Re: 2.6.20.3 - possible recursive locking detected - in XFS
Date: Thu, 26 Apr 2007 09:33:45 +1000	[thread overview]
Message-ID: <20070425233345.GN48531920@melbourne.sgi.com> (raw)
In-Reply-To: <200704251116.57737.jesper.juhl@gmail.com>

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.

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group

  reply	other threads:[~2007-04-25 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25  9:16 2.6.20.3 - possible recursive locking detected - in XFS Jesper Juhl
2007-04-25 23:33 ` David Chinner [this message]
2007-04-26 10:17   ` Jesper Juhl
2007-04-26 17:13     ` Eric Sandeen
2007-04-27  7:06       ` Klaus Strebel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070425233345.GN48531920@melbourne.sgi.com \
    --to=dgc@sgi.com \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=xfs-masters@oss.sgi.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox