linux-kernel - Re: [PATCH v7u1 27/31] x86, kdump: remove crashkernel range find limit for 64bit

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: <CAE9FiQWo2LfGuGpZdWYapU-VxHuwDkGbAdqfBKif9XzH59QBkw@mail.gmail.com>
Date:	Mon, 14 Jan 2013 10:18:39 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Borislav Petkov <bp@...en8.de>, Yinghai Lu <yinghai@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jan Kiszka <jan.kiszka@....de>,
	Jason Wessel <jason.wessel@...driver.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7u1 27/31] x86, kdump: remove crashkernel range find
 limit for 64bit

On Mon, Jan 14, 2013 at 7:43 AM, Borislav Petkov <bp@...en8.de> wrote:
> On Thu, Jan 03, 2013 at 04:48:47PM -0800, Yinghai Lu wrote:
>> Now kexeced kernel/ramdisk could be above 4g, so remove 896 limit for
>> 64bit.
>>
>> Signed-off-by: Yinghai Lu <yinghai@...nel.org>
>> ---
>>  arch/x86/kernel/setup.c |    4 +---
>>  1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
>> index c58497e..6adbc45 100644
>> --- a/arch/x86/kernel/setup.c
>> +++ b/arch/x86/kernel/setup.c
>> @@ -501,13 +501,11 @@ static void __init memblock_x86_reserve_range_setup_data(void)
>>  /*
>>   * Keep the crash kernel below this limit.  On 32 bits earlier kernels
>>   * would limit the kernel to the low 512 MiB due to mapping restrictions.
>> - * On 64 bits, kexec-tools currently limits us to 896 MiB; increase this
>> - * limit once kexec-tools are fixed.
>
> Does this mean that kexec-tools has been fixed too?

with the patcheset that i sent to kexec-tools mailing list.
--
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/