Re: [PATCH security-next v3 00/29] LSM: Explict LSM ordering

2018-09-29 Thread Tetsuo Handa
On 2018/09/29 5:01, Kees Cook wrote: > On Fri, Sep 28, 2018 at 8:55 AM, Casey Schaufler > wrote: >> On 9/24/2018 5:18 PM, Kees Cook wrote: >>> v3: >>> - add CONFIG_LSM_ENABLE and refactor resulting logic >> >> Kees, you can add my >> >> Reviewed-by:Casey Schaufler >> >> for this entire p

Re: [PATCH security-next v3 00/29] LSM: Explict LSM ordering

2018-09-29 Thread Kees Cook
On Sat, Sep 29, 2018 at 3:48 AM, Tetsuo Handa wrote: > On 2018/09/29 5:01, Kees Cook wrote: >> On Fri, Sep 28, 2018 at 8:55 AM, Casey Schaufler >> wrote: >>> On 9/24/2018 5:18 PM, Kees Cook wrote: v3: - add CONFIG_LSM_ENABLE and refactor resulting logic >>> >>> Kees, you can add my >>>

Re: [PATCH security-next v3 00/29] LSM: Explict LSM ordering

2018-09-29 Thread John Johansen
On 09/29/2018 03:48 AM, Tetsuo Handa wrote: > On 2018/09/29 5:01, Kees Cook wrote: >> On Fri, Sep 28, 2018 at 8:55 AM, Casey Schaufler >> wrote: >>> On 9/24/2018 5:18 PM, Kees Cook wrote: v3: - add CONFIG_LSM_ENABLE and refactor resulting logic >>> >>> Kees, you can add my >>> >>>

Re: [PATCH security-next v3 00/29] LSM: Explict LSM ordering

2018-09-29 Thread Tetsuo Handa
On 2018/09/30 3:18, Kees Cook wrote: >> Just wondering what is "__lsm_name_##lsm" for... >> >> +#define DEFINE_LSM(lsm) >>\ >> + static const char __lsm_name_##lsm[] __initconst\ >> + __aligned(1) = #lsm;