From: Dave Chinner <david@fromorbit.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, xfs@oss.sgi.com, linux-mm@kvack.org
Subject: Re: 3.14.0-rc2: WARNING: at mm/slub.c:1007
Date: Fri, 14 Feb 2014 12:14:53 +1100 [thread overview]
Message-ID: <20140214011453.GP13997@dastard> (raw)
In-Reply-To: <alpine.DEB.2.19.4.1402131531290.6233@trent.utfs.org>
On Thu, Feb 13, 2014 at 03:34:19PM -0800, Christian Kujau wrote:
> On Fri, 14 Feb 2014 at 09:26, Dave Chinner wrote:
> > > after upgrading from 3.13-rc8 to 3.14.0-rc2 on this PowerPC G4 machine,
> > > the WARNING below was printed.
> > >
> > > Shortly after, a lockdep warning appeared (possibly related to my
> > > post to the XFS list yesterday[0]).
> >
> > Unlikely.
>
> OK, so the "possible irq lock inversion dependency detected" is a lockdep
> regression, as you explained in the xfs-list thread. What about the
> "RECLAIM_FS-safe -> RECLAIM_FS-unsafe lock order detected" warning - I
> haven't seen it again though, only once with 3.14.0-rc2.
That was also an i_lock/mmapsem issue, so it's likely to be the same
root cause. I'm testing a fix for it at the moment.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-02-14 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-13 19:53 Christian Kujau
2014-02-13 20:01 ` Christian Kujau
2014-02-13 22:14 ` David Rientjes
2014-02-13 22:26 ` Dave Chinner
2014-02-13 23:34 ` Christian Kujau
2014-02-14 1:14 ` Dave Chinner [this message]
2014-02-14 1:22 ` Christian Kujau
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=20140214011453.GP13997@dastard \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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