linux-kernel - Re: 3.14.0-rc2: WARNING: at mm/slub.c:1007

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:	Fri, 14 Feb 2014 12:14:53 +1100
From:	Dave Chinner <david@...morbit.com>
To:	Christian Kujau <lists@...dbynature.de>
Cc:	LKML <linux-kernel@...r.kernel.org>, xfs@....sgi.com,
	linux-mm@...ck.org
Subject: Re: 3.14.0-rc2: WARNING: at mm/slub.c:1007

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@...morbit.com
--
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/