| 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: <CACLa4pspOFx638fn6aDHpESVZrKmWCnrO999qoO+Mna4ccF_7g@mail.gmail.com> Date: Wed, 16 May 2012 10:13:37 -0400 From: Eric Paris <eparis@...isplace.org> To: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Mimi Zohar <zohar@...ux.vnet.ibm.com>, Mimi Zohar <zohar@...ibm.com>, linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org, Al Viro <viro@...iv.linux.org.uk>, Stephen Smalley <sds@...ho.nsa.gov> Subject: Re: [PATCH] vfs: fix IMA lockdep circular locking dependency On Tue, May 15, 2012 at 8:37 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote: > It does change some things, like say that "->mmap_file()" is only ever > called for actual files, not for anonymous mappings. It doesn't seem > to be sensible to have a security model for anonymous mappings - > there's nothing there to really target. Whatever. So we would have no checks for anonymous mappings? We actually do have some controls around them today http://www.akkadia.org/drepper/selinux-mem.html It's mostly around W+X memory. (or was W now X memory) Admittedly with the growing prevalence of JiT stuff we are using those protections less and less and less.... Not certain how happy some will be to see them completely disappear.... -- 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