From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: xfs@oss.sgi.com
Subject: Re: 3.14-rc2: RECLAIM_FS-safe -> RECLAIM_FS-unsafe lock order detected
Date: Fri, 14 Feb 2014 09:11:28 +1100 [thread overview]
Message-ID: <20140213221128.GJ13997@dastard> (raw)
In-Reply-To: <alpine.DEB.2.19.4.1402131153300.6233@trent.utfs.org>
On Thu, Feb 13, 2014 at 11:56:36AM -0800, Christian Kujau wrote:
> On Wed, 12 Feb 2014 at 00:11, Christian Kujau wrote:
> > After upgrading from 3.13-rc8 to 3.14-rc2 on this PowerPC G4 machine, this
> > happened:
>
> Yesterday a slighly different lockdep warning was printed:
>
> =========================================================
> [ INFO: possible irq lock inversion dependency detected ]
> 3.14.0-rc2 #1 Tainted: G W
> ---------------------------------------------------------
> kswapd0/279 just changed the state of lock:
> (&(&ip->i_lock)->mr_lock){++++.?}, at: [<c01c213c>]
> xfs_free_eofblocks+0xe8/0x2e0
> but this lock took another, RECLAIM_FS-unsafe lock in the past:
> (&mm->mmap_sem){++++++}
>
> and interrupts could create inverse lock ordering between them.
False positive - it's confusing directory locking orders with
regular files. Already reported, but the devs responsible for the
lockdep regression have not responded. Looks like I'll have to
fix it myself. I'll see what I can do today.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-02-13 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-12 8:11 3.14-rc2: RECLAIM_FS-safe -> RECLAIM_FS-unsafe lock order detected Christian Kujau
2014-02-12 8:22 ` Christian Kujau
2014-02-12 11:05 ` Hugh Dickins
2014-02-13 19:56 ` Christian Kujau
2014-02-13 20:42 ` Chris Murphy
2014-02-13 22:11 ` Dave Chinner [this message]
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=20140213221128.GJ13997@dastard \
--to=david@fromorbit.com \
--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