linux-kernel - Re: 2.6.21-rc5-mm4

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:	Tue, 3 Apr 2007 15:59:33 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Badari Pulavarty <pbadari@...il.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.21-rc5-mm4

On Tue, 3 Apr 2007, Badari Pulavarty wrote:

> > > SLUB code hangs my ppc64 machine on boot.
> > 
> > Could you enable NMI or something and get me a stackdump? PPC is notorious 
> > for having strange NUMA issues. Any fallbacks from node 0 on bootstrap? Is 
> > there memory on node 0?
> 
> 
> Seems to be an issue with calibrate_delay() spinning in a tight
> loop :(
> 
> BTW, machine boots fine with SLAB code - not sure why ?

SLUB does not guarantee the special casing that SLAB provides for 
page sized allocations via kmalloc. SLAB aligns page sized allocations on 
page boundaries and does not allow full debugging of page sized 
allocations in order to keep these slabs on page sized boundaries.

I suspect this is related. I could add the same special casing to SLUB. 
But I really wish we would get rid of special slab behavior depending on 
the size of the slab. Maybe there is no way around it. Sigh.

What is the data that calibrate delay is looking at?
-
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/