From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com
Subject: Re: lockdep: inconsistent lock state
Date: Mon, 28 Dec 2009 08:27:00 +1100 [thread overview]
Message-ID: <20091227212700.GA7613@discord.disaster> (raw)
In-Reply-To: <alpine.DEB.2.01.0912261255380.3483@bogon.housecafe.de>
On Sat, Dec 26, 2009 at 01:07:49PM -0800, Christian Kujau wrote:
> Hi,
>
> during tests with bonnie++ on an XFS filesystem, the warning below is
> issued. From the message's timestamps, the warning occurs during the
> "Create files in sequential order" phase. I've put a few more details and
> the config here: http://nerdbynature.de/bits/2.6.33-rc2/xfs_ilock
>
> Something similar has been reported in http://lkml.org/lkml/2009/2/20/269
> (for 2.6.29-rc5) and a fix for this false positive made its way into
> mainline as ed93ec3907f063268ced18728d0653f6199d100c - so I take it this
> is a different issue then?
This is the usual false positive that is detected - XFS takes locks in
reclaim that it also takes in non-reclaim paths. The reclaim path
from kswapd inverts lock ordering and so we get this report. This
case has never been a deadlock case because an inode in reclaim
cannot be referenced by any other path, so once again it is a
false positive....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-27 21:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-26 21:07 lockdep: inconsistent lock state Christian Kujau
2009-12-27 21:27 ` Dave Chinner [this message]
2009-12-27 22:01 ` Christian Kujau
2010-01-06 17:36 ` Christoph Hellwig
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=20091227212700.GA7613@discord.disaster \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--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