| 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
| ||
|
Date: Fri, 23 Apr 2010 08:43:17 +0200 From: Vitaly Mayatskikh <v.mayatskih@...il.com> To: ebiederm@...ssion.com (Eric W. Biederman) Cc: Cong Wang <amwang@...hat.com>, Vivek Goyal <vgoyal@...hat.com>, Vitaly Mayatskikh <v.mayatskih@...il.com>, linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Haren Myneni <hbabu@...ibm.com>, Neil Horman <nhorman@...driver.com>, kexec@...ts.infradead.org Subject: Re: [PATCH 0/5] Add second memory region for crash kernel At Thu, 22 Apr 2010 22:42:25 -0700, Eric W. Biederman wrote: > > We have observed that on a machine which has 66G memory, when we do > > crashkernel=1G@4G, kexec failed to load the crash kernel, but the memory > > reservation _did_ succeed. > > Did you try loading vmlinux? If not this sounds like the fact that > /sbin/kexec doesn't realize it can boot a 64bit bzImage in 64bit > mode. /sbin/kexec currently has hardcoded limitations for bzImage and initrd: include/x86/x86-linux.h: #define DEFAULT_INITRD_ADDR_MAX 0x37FFFFFF #define DEFAULT_BZIMAGE_ADDR_MAX 0x37FFFFFF This is easy to override. However, purgatory code still wants to see kernel below 2 Gb (32-bit signed relocations). -- wbr, Vitaly -- 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/
Powered by blists - more mailing lists