| 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
| ||
|
Message-ID: <51072147.9090306@zytor.com> Date: Mon, 28 Jan 2013 17:09:27 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Thomas Renninger <trenn@...e.de> CC: yinghai@...nel.org, x86@...nel.org, linux-kernel@...r.kernel.org, kexec@...ts.infradead.org, vgoyal@...hat.com, horms@...ge.net.au Subject: Re: [PATCH 1/2] x86 e820: Check for exactmap appearance when parsing first memmap option On 01/22/2013 07:20 AM, Thomas Renninger wrote: > From: Yinghai Lu <yinghai@...nel.org> > > memmap=exactmap will throw away all original, but also until then > user defined (through other provided memmap= parameters) areas. > That means all memmap= boot parameters passed before a memmap=exactmap > parameter are not recognized. > Without this fix: > memmap=x@y memmap=exactmap memmap=i#k > only i#k would get recognized. > > This is wrong, this fix will only throw away all original e820 areas once > when memmap=exactmap is found in the whole boot command line and before > any other memmap= option is parsed. > I don't understand why this is wrong. The kernel command line is always parsed from left to right, and I don't see anything inherently problematic with that with something like a big hammer like exactmap. -hpa -- 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