[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.21.2003271128230.17915@namei.org>
Date: Fri, 27 Mar 2020 11:28:35 +1100 (AEDT)
From: James Morris <jmorris@...ei.org>
To: KP Singh <kpsingh@...omium.org>
cc: linux-kernel@...r.kernel.org, bpf@...r.kernel.org,
linux-security-module@...r.kernel.org,
Brendan Jackman <jackmanb@...gle.com>,
Florent Revest <revest@...gle.com>,
Kees Cook <keescook@...omium.org>,
Casey Schaufler <casey@...aufler-ca.com>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Paul Turner <pjt@...gle.com>, Jann Horn <jannh@...gle.com>,
Florent Revest <revest@...omium.org>,
Brendan Jackman <jackmanb@...omium.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH bpf-next v7 2/8] security: Refactor declaration of LSM
hooks
On Thu, 26 Mar 2020, KP Singh wrote:
> From: KP Singh <kpsingh@...gle.com>
>
> The information about the different types of LSM hooks is scattered
> in two locations i.e. union security_list_options and
> struct security_hook_heads. Rather than duplicating this information
> even further for BPF_PROG_TYPE_LSM, define all the hooks with the
> LSM_HOOK macro in lsm_hook_defs.h which is then used to generate all
> the data structures required by the LSM framework.
>
> The LSM hooks are defined as:
>
> LSM_HOOK(<return_type>, <default_value>, <hook_name>, args...)
>
> with <default_value> acccessible in security.c as:
>
> LSM_RET_DEFAULT(<hook_name>)
>
> Signed-off-by: KP Singh <kpsingh@...gle.com>
> Reviewed-by: Brendan Jackman <jackmanb@...gle.com>
> Reviewed-by: Florent Revest <revest@...gle.com>
> Reviewed-by: Kees Cook <keescook@...omium.org>
> Reviewed-by: Casey Schaufler <casey@...aufler-ca.com>
Acked-by: James Morris <jamorris@...ux.microsoft.com>
--
James Morris
<jmorris@...ei.org>
Powered by blists - more mailing lists