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

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: <1defaf580706110858r16b1b88bg2346734379574b52@mail.gmail.com>
Date:	Mon, 11 Jun 2007 17:58:12 +0200
From:	"Håvard Skinnemoen" <hskinnemoen@...il.com>
To:	"Paul Mundt" <lethal@...ux-sh.org>,
	"Haavard Skinnemoen" <hskinnemoen@...el.com>,
	"Christoph Lameter" <clameter@....com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: kernel BUG at mm/slub.c:3689!

On 6/11/07, Paul Mundt <lethal@...ux-sh.org> wrote:
> On Mon, Jun 11, 2007 at 04:19:26PM +0200, Haavard Skinnemoen wrote:
> > I think the combination that triggered this bug was:
> >   * CONFIG_SLUB_DEBUG=y
> >   * ARCH_KMALLOC_MINALIGN=32
> >   * slub_debug not set at the command line
> >
> ARCH_KMALLOC_MINALIGN and ARCH_SLAB_MINALIGN are both in bytes
> (ARCH_KMALLOC_MINALIGN used to be defined as BYTES_PER_WORD) if I recall
> correctly, are you sure this is what you want?

Yeah, I actually defined it to L1_CACHE_BYTES. The idea is to avoid
cacheline sharing between different kmalloc() allocations, which may
mess up DMA transfers. So 32 bytes alignment is indeed what I want.

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