| 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: <20080502072226.GB713@elte.hu> Date: Fri, 2 May 2008 09:22:26 +0200 From: Ingo Molnar <mingo@...e.hu> To: Jiri Slaby <jirislaby@...il.com> Cc: mingo@...hat.com, linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>, tglx@...utronix.de, hpa@...or.com Subject: Re: [PATCH 1/2] x86_64: fix mm.txt documentation * Jiri Slaby <jirislaby@...il.com> wrote: > Commit 85eb69a16aab5a394ce043c2131319eae35e6493 introduced 512 MiB > sized kernel and 1.5 GiB sized module space but omitted to change > documentation properly. Fix that. thanks Jiri, applied. > [Wasn't the hole intentional protection hole?] > -ffffffff80000000 - ffffffff82800000 (=40 MB) kernel text mapping, from phys 0 > -... unused hole ... > -ffffffff88000000 - fffffffffff00000 (=1919 MB) module mapping space > +ffffffff80000000 - ffffffffa0000000 (=512 MB) kernel text mapping, from phys 0 > +ffffffffa0000000 - fffffffffff00000 (=1536 MB) module mapping space yep, the image was in a 128 MB chunk from which 88 MB was left empty and modules started at the next 128 MB boundary. The largest image i ever had was around 44MB, so i doubt it's an issue in practice. Mind doing a patch that reinstates it, by lowering the 512 image size limit to 508 MB? [4MB should be more than enough in practice] Ingo -- 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