linux-kernel - Re: [PATCH] kernel parameter vmalloc size fix

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: <48568A69.6040800@zytor.com>
Date:	Mon, 16 Jun 2008 08:44:41 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Dave Young <hidave.darkstar@...il.com>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH] kernel parameter vmalloc size fix

Ingo Molnar wrote:
> 
> hm. Why dont we instead add the size of the hole to the 
> __VMALLOC_RESERVE value instead? There's nothing inherently bad about 
> using vmalloc=16m. The VM area hole is really a kernel-internal 
> abstraction that should not be visible in the usage of the parameter.
> 

Well, the question is are we taking it away from RAM or away from 
vmalloc... there aren't really any other alternatives.

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