netdev - Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

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]

Message-ID: <alpine.DEB.2.00.1111220900330.25785@router.home>
Date:	Tue, 22 Nov 2011 09:02:27 -0600 (CST)
From:	Christoph Lameter <cl@...ux.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Christian Kujau <lists@...dbynature.de>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	"Alex,Shi" <alex.shi@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	Pekka Enberg <penberg@...nel.org>,
	Matt Mackall <mpm@...enic.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Tejun Heo <tj@...nel.org>
Subject: Re: WARNING: at mm/slub.c:3357, kernel BUG at mm/slub.c:3413

On Tue, 22 Nov 2011, Eric Dumazet wrote:

> Le mardi 22 novembre 2011 à 08:46 -0600, Christoph Lameter a écrit :
> > On Tue, 22 Nov 2011, Eric Dumazet wrote:
> >
> > > I trigger a bug in less than 10 secondes, with this running while a
> > > "make -j16 " kernel build is run.
> > >
> > > while :; do slabinfo -v; done
> >
> > Hmm.... Yeah there was limited testing on the debug features. There could
> > be something amiss there. Need to review the validation interactions with
> > the new code.
> >
> >
>
> Hmm... yes, we probably should take a look.

Allright there is an obvious issue if debugging is off since the lockless
paths do not take the page lock in that case but the validation logic
does. Did you run the test with debugging on or off?

Not sure what the solution is but the simplest would be to disable
validation if lockless is active.