linux-kernel - Re: [PATCH 0/3] Early use of boot service memory

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:	Wed, 13 Nov 2013 14:49:42 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	jerry.hoemann@...com
CC:	rob@...dley.net, tglx@...utronix.de, mingo@...hat.com,
	x86@...nel.org, matt.fleming@...el.com, yinghai@...nel.org,
	penberg@...nel.org, akpm@...ux-foundation.org,
	linux-doc@...r.kernel.org, linux-efi@...r.kernel.org,
	vgoyal@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/3] Early use of boot service memory

On 11/13/2013 02:45 PM, jerry.hoemann@...com wrote:
> 
> The changes in 3.9 to allow crash kernel to be allocated high helps. 
> But as you say, the default is still to allocate crash kernel low and
> still susceptible to this problem.  So, a kdump expert can work around it.
> But, not everyone is a kdump expert.
> 
> So, we can work to change the default, or encourage the distros
> to always allocate high.  Or, we change the call to efi_reserve_boot_services
> not apply to all platforms.
> 
> The problems for pre 3.9 based distros is worse as they don't have
> ability to allocate crash kernel high.
> 

But they won't have your new option, either, and that is still horribly
manual and system-dependent.

In other words, allocating the crashkernel high has ALL the advantages,
plus a few more, and NONE of the disadvantages.

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