linux-kernel - Re: BUG at mm/slub.c:374

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] [day] [month] [year] [list]

Date:	Thu, 10 May 2012 09:21:14 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	richard -rw- weinberger <richard.weinberger@...il.com>
cc:	LKML <linux-kernel@...r.kernel.org>, linux-mm@...ck.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>
Subject: Re: BUG at mm/slub.c:374

On Thu, 10 May 2012, richard -rw- weinberger wrote:

> On Wed, May 9, 2012 at 4:14 PM, Christoph Lameter <cl@...ux.com> wrote:
> > On Wed, 9 May 2012, richard -rw- weinberger wrote:
> >
> >> A few minutes ago I saw this BUG within one of my KVM machines.
> >> Config is attached.
> >
> > Interrupts on in __cmpxchg_double_slab called from __slab_alloc? Does KVM
> > do some tricks with interrupt flags? I do not see how that can be
> > otherwise since __slab_alloc disables interrupts on entry and reenables on
> > exit.
>
> Dunno.
> So far I've seen this BUG only once. :-\

Hmmm... allocate_slab() does some dangerous games with the "flag" variable
which determines if interrupts are to be reenabled and disabled but I
cannot see how it could have the effect that you are seeing.

--
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/