linux-kernel - CONFIG_NR_CPUS limit for 32-bit

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

Message-Id: <48AEEB1E.76E4.0078.0@novell.com>
Date:	Fri, 22 Aug 2008 15:36:46 +0100
From:	"Jan Beulich" <jbeulich@...ell.com>
To:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>, <travis@....com>
Cc:	<linux-kernel@...r.kernel.org>
Subject: CONFIG_NR_CPUS limit for 32-bit

Given that the fixmap area size depends on NR_CPUS and that it can't
possibly cover 4096 CPUs (its size would be beyond 200Mb if I put things
together correctly, whereas the vmalloc area [of which the fixmap area is
a sub-portion] by default is 128MB) I can't see how this new limit ought to
even boot on any system.

Therefore I wonder whether the range shouldn't be restricted for X86_32.

Jan

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