linux-kernel - Re: [patch 01/28] cpu alloc: The allocator

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

Message-Id: <20071113.175208.168903694.davem@davemloft.net>
Date:	Tue, 13 Nov 2007 17:52:08 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	andi@...stfloor.org
Cc:	clameter@....com, akpm@...ux-foundation.org,
	linux-mm@...r.kernel.org, linux-kernel@...r.kernel.org,
	dada1@...mosbay.com, schwidefsky@...ibm.com
Subject: Re: [patch 01/28] cpu alloc: The allocator

From: Andi Kleen <andi@...stfloor.org>
Date: Wed, 14 Nov 2007 02:06:28 +0100

> David Miller <davem@...emloft.net> writes:
> >
> > The problem is that for the non-virtualized case this patch bloats up
> > the BSS section to be more than 8MB in size.  Sparc64 kernel images
> > cannot be more than 8MB in size total due to various boot loader and
> > firmware limitations.
> 
> I recently ran into a similar problem with x86-64 and large BSS from
> lockdep conflicting with a 16MB kdump kernel. Solution was to do
> another early allocator before bootmem and then move the tables into
> there.

Yes, I've run into similar problems with lockdep as well.
I had to build an ultra minimalized kernel to get it to
boot on my Niagara boxes.

I think I even looked at the same lockdep code, and I'd
appreciate it if you'd submit your fix for this if you
haven't already.
-
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/