Date: Thu, 29 Jun 2017 21:28:11 +0200 From: Salvatore Mesoraca <s.mesoraca16@...il.com> To: Kees Cook <keescook@...omium.org> Cc: LKML <linux-kernel@...r.kernel.org>, linux-security-module <linux-security-module@...r.kernel.org>, "kernel-hardening@...ts.openwall.com" <kernel-hardening@...ts.openwall.com>, Brad Spengler <spender@...ecurity.net>, PaX Team <pageexec@...email.hu>, Casey Schaufler <casey@...aufler-ca.com>, James Morris <james.l.morris@...cle.com>, "Serge E. Hallyn" <serge@...lyn.com>, Linux-MM <linux-mm@...ck.org>, "x86@...nel.org" <x86@...nel.org>, Jann Horn <jannh@...gle.com>, Christoph Hellwig <hch@...radead.org>, Thomas Gleixner <tglx@...utronix.de>, Stephen Smalley <sds@...ho.nsa.gov>, John Johansen <john.johansen@...onical.com> Subject: Re: [RFC v2 3/9] Creation of "check_vmflags" LSM hook 2017-06-28 1:05 GMT+02:00 Kees Cook <keescook@...omium.org>: > On Thu, Jun 15, 2017 at 9:42 AM, Salvatore Mesoraca > <s.mesoraca16@...il.com> wrote: >> Creation of a new LSM hook to check if a given configuration of vmflags, >> for a new memory allocation request, should be allowed or not. >> It's placed in "do_mmap", "do_brk_flags" and "__install_special_mapping". > > I like this. I think this is something the other LSMs should be > checking too. (Though I wonder if it would be helpful to include the > VMA in the hook, though it does exist yet, so... hmm.) For the particular case of my LSM and the type of check it does, the VMA isn't needed, of course. Maybe some other LSM can benefit from it, but it depends on what they want to do with this hook. Looking forward to feedback from potential future users. Thank you for your interest. Salvatore
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.