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, 3 Oct 2008 10:02:44 +0200 From: Ingo Molnar <mingo@...e.hu> To: "Kirill A. Shutemov" <kirill@...temov.name> Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: Re: [PATCH] x86_64: Implement personality ADDR_LIMIT_32BIT * Kirill A. Shutemov <kirill@...temov.name> wrote: > - /* for MAP_32BIT mappings we force the legact mmap base */ > - if (!test_thread_flag(TIF_IA32) && (flags & MAP_32BIT)) > + /* for MAP_32BIT mappings and ADDR_LIMIT_32BIT personality we force the > + * legact mmap base > + */ please use the customary multi-line comment style: /* * Comment ..... * ...... goes here: */ and you might use the opportunity to fix the s/legact/legacy typo as well. but more generally, we already have ADDR_LIMIT_3GB support on x86. Why should support for ADDR_LIMIT_32BIT be added? 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