linux-kernel - Re: [slub] WARNING: CPU: 1 PID: 1 at mm/slub.c:992 deactivate

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140207024602.GA12062@localhost>
Date:	Fri, 7 Feb 2014 10:46:02 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	David Rientjes <rientjes@...gle.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Pekka Enberg <penberg@...nel.org>, linux-mm@...ck.org,
	linux-kernel@...r.kernel.org
Subject: Re: [slub] WARNING: CPU: 1 PID: 1 at mm/slub.c:992 deactivate_slab()

On Thu, Feb 06, 2014 at 01:41:10PM -0800, David Rientjes wrote:
> On Wed, 5 Feb 2014, David Rientjes wrote:
> 
> > Ah, that's because the patch didn't go through Pekka's slab tree but went 
> > into -mm instead so we have to wait for another -mm.  However, the traces 
> > from linux-next-20140204 that you provided indicate it's the same problem 
> > and should be fixed with that patch, so let's wait for another mmotm to be 
> > released.
> > 
> 
> Ok, "mm/slub.c: list_lock may not be held in some circumstances" is in 
> linux-next so let me know if this reproduces!

Yeah, linux-next 20140206 no longer has this WARNING!

Thanks,
Fengguang
--
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/