[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJHCu1LdGEEFkpAZqVYYORfXxTA+VuHUv2Pv+rYMN1Nt4KGVBg@mail.gmail.com>
Date: Tue, 13 Jun 2017 09:55:30 +0200
From: Salvatore Mesoraca <s.mesoraca16@...il.com>
To: Casey Schaufler <casey@...aufler-ca.com>
Cc: kernel list <linux-kernel@...r.kernel.org>,
linux-security-module@...r.kernel.org,
Kernel Hardening <kernel-hardening@...ts.openwall.com>,
Brad Spengler <spender@...ecurity.net>,
PaX Team <pageexec@...email.hu>,
Kees Cook <keescook@...omium.org>,
James Morris <james.l.morris@...cle.com>,
"Serge E. Hallyn" <serge@...lyn.com>, linux-mm@...ck.org
Subject: Re: [PATCH 05/11] Creation of "check_vmflags" LSM hook
2017-06-12 23:31 GMT+02:00 Casey Schaufler <casey@...aufler-ca.com>:
> Have the hook return a value and return that rather
> than -EPERM. That way a security module can choose an
> error that it determines is appropriate. It is possible
> that a module might want to deny the access for a reason
> other than lack of privilege.
> [...]
>
> Same here
>
> [...]
>
> And here.
Yes, I think you are right. I'll fix it in the next version.
Thank you very much for taking the time to review my patch.
Powered by blists - more mailing lists