| 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: <alpine.DEB.2.11.1410281828340.5308@nanos> Date: Tue, 28 Oct 2014 18:29:07 +0100 (CET) From: Thomas Gleixner <tglx@...utronix.de> To: "H. Peter Anvin" <hpa@...or.com> cc: Minfei Huang <mnfhuang@...il.com>, mingo@...hat.com, x86@...nel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] mm: Avoid overlap the fixmap area on i386 On Tue, 28 Oct 2014, H. Peter Anvin wrote: > On 10/28/2014 04:06 AM, Thomas Gleixner wrote: > >> > >> The available address we can use is lower than FIXADDR_BOOT_START. So > >> We will set the kmap boundary below the FIXADDR_BOOT_START, if configure > >> the high memory. > >> > >> If we configure the high memory, the vmalloc reserve area should end > >> up to PKMAP_BASE, otherwise should end up to FIXADDR_BOOT_START. > > > > Which is not really a problem, because the FIXADDR_BOOT area is only > > used during boot for early_ioremap() and it's unused when ioremap() is > > functional. vmalloc becomes available after early boot so the > > FIXADDR_BOOT area is available for reuse. > > > > Given the very limited address space available on i386, it would be > extremely undesirable to not reuse address space when possible. Fair enough. Then we should do that for the highmem=y case as well. Thanks, tglx -- 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