linux-kernel - Re: [PATCH -v4 0/4] x86, kdump: Fix crashkernel high with old kexec-tools

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: <20130410202842.GG6602@redhat.com>
Date:	Wed, 10 Apr 2013 16:28:42 -0400
From:	Vivek Goyal <vgoyal@...hat.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...e.hu>,
	"H. Peter Anvin" <hpa@...or.com>, WANG Chao <chaowang@...hat.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -v4 0/4] x86, kdump: Fix crashkernel high with old
 kexec-tools

On Wed, Apr 10, 2013 at 12:39:15PM -0700, Yinghai Lu wrote:
> Vivek found some problems with old kexec-tools.
> 
> We keep the old crashkernel=X to old behavoir, so it will not break
> old kexec-tools.
> Add crashkernel=X,high to support new kexec-tools that supports loading high.
> when high is used, memblock will search from top to low.
> if the allocated one is above 4G, kernel will try to auto allocate
> 72M under 4G for swiotlb.
> user could crashkernel=Y,low to change 72M to other value.
> 
> -v2:	reorder the patch sequences
> 	crashkernel=X,high, crashkernel=Y,low only handle simple form.
> 	crashkernel=X will override crashkernel=X;high crashkernel=Y;low
> -v3:	update description in kernel-parameters.txt
> 	update get_last_crashkernel and _simple checking about suffix.
> -v4:	update to use ,high again, and also not abuse parse_crashkernel_simple
> 

This series looks good to me.

Acked-by: Vivek Goyal <vgoyal@...hat.com>

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