| 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: Tue, 8 Jan 2008 11:11:05 +0530 From: Dhaval Giani <dhaval@...ux.vnet.ibm.com> To: "H. Peter Anvin" <hpa@...or.com> Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Thomas Gleixer <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, vgoyal@...hat.com, hbabu@...ibm.com, kexec@...ts.infradead.org Subject: Re: [PATCH] i386: handle an initrd in highmem (version 2) On Mon, Jan 07, 2008 at 09:02:53PM -0800, H. Peter Anvin wrote: > The boot protocol has until now required that the initrd be located in > lowmem, which makes the lowmem/highmem boundary visible to the boot > loader. This was exported to the bootloader via a compile-time > field. Unfortunately, the vmalloc= command-line option breaks this > part of the protocol; instead of adding yet another hack that affects > the bootloader, have the kernel relocate the initrd down below the > lowmem boundary inside the kernel itself. > > Note that this does not rely on HIGHMEM being enabled in the kernel. > > Signed-off-by: H. Peter Anvin <hpa@...or.com> > --- > Fix crash on NUMA reported by Dhaval Giani (reported as being a kexec issue.) > Yep, it does that. Just tested that on top of the x86 git tree (the mm queue). It boots. Tested-by: Dhaval Giani <dhaval@...ux.vnet.ibm.com> -- regards, Dhaval -- 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