| 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: Thu, 10 Jul 2014 11:00:06 -0700 From: Yinghai Lu <yinghai@...nel.org> To: Matt Fleming <matt@...sole-pimps.org> Cc: Matt Fleming <matt.fleming@...el.com>, "H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>, linux-efi@...r.kernel.org, Linux Kernel Mailing List <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] x86, eboot: Support initrd loaded above 4G On Wed, Jul 9, 2014 at 11:26 AM, Matt Fleming <matt@...sole-pimps.org> wrote: > On Wed, 18 Jun, at 03:28:19PM, Matt Fleming wrote: >> On Sat, 14 Jun, at 12:23:41PM, Yinghai Lu wrote: >> > For boot efi kernel directly without bootloader. >> > If the kernel support XLF_CAN_BE_LOADED_ABOVE_4G, we should >> > not limit initrd under hdr->initrd_add_max. > > Well, fooey. This patch breaks one of my ASUS machines. It appears some > firmware implementations exhibit issues reading directly into a buffer > above the 4GB mark. > > I haven't diagnosed exactly what goes wrong with the buffer (i.e. in > what way it becomes corrupt), but I should really do that before > thinking of how to fix this. > > I'll keep you posted, I just wanted to give you a heads up that things > are screwy in this area. Oh, no. so efi could allocate buffer above 4g but can not access it? Yinghai -- 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