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, 11 Jan 2013 12:06:48 -0800 From: "H. Peter Anvin" <hpa@...or.com> To: Yinghai Lu <yinghai@...nel.org> CC: Thomas Renninger <trenn@...e.de>, MUNEDA Takahiro <muneda.takahiro@...fujitsu.com>, Takao Indoh <indou.takao@...fujitsu.com>, linux-pci@...r.kernel.org, x86@...nel.org, linux-kernel@...r.kernel.org, andi@...stfloor.org, tokunaga.keiich@...fujitsu.com, kexec@...ts.infradead.org, hbabu@...ibm.com, mingo@...hat.com, ddutile@...hat.com, vgoyal@...hat.com, ishii.hironobu@...fujitsu.com, bhelgaas@...gle.com, tglx@...utronix.de, khalid@...ehiking.org, horms@...ge.net.au Subject: Re: [PATCH] x86 e820: only void usable memory areas in memmap=exactmap case On 01/11/2013 11:59 AM, Yinghai Lu wrote: > On Fri, Jan 11, 2013 at 10:24 AM, Thomas Renninger <trenn@...e.de> wrote: >>> We may need to keep exactmap intact. >> Why? >> Kexec/kdump should have been the only user? >> If older/current kexec calls still add ACPI maps via memmap=X#Y, >> they should already exist in the original e820 map and fall off or >> get glued to one region if (wrongly) overlapping via sanitize_map. > > No, kexec/kdump is not the only user for memmap=exactmap. > Who is using it then, since you seem to know? -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