[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <447298d65b497fb1a7f8d47c4f1a3137eba24511.camel@huaweicloud.com>
Date: Thu, 26 Oct 2023 17:12:03 +0200
From: Roberto Sassu <roberto.sassu@...weicloud.com>
To: Paul Moore <paul@...l-moore.com>, jmorris@...ei.org,
serge@...lyn.com
Cc: linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, zohar@...ux.ibm.com,
linux-integrity@...r.kernel.org,
Roberto Sassu <roberto.sassu@...wei.com>
Subject: Re: [PATCH] security: Don't yet account for IMA in LSM_CONFIG_COUNT
calculation
On Thu, 2023-10-26 at 10:48 -0400, Paul Moore wrote:
> On Oct 26, 2023 Roberto Sassu <roberto.sassu@...weicloud.com> wrote:
> >
> > Since IMA is not yet an LSM, don't account for it in the LSM_CONFIG_COUNT
> > calculation, used to limit how many LSMs can invoke security_add_hooks().
> >
> > Signed-off-by: Roberto Sassu <roberto.sassu@...wei.com>
> > ---
> > security/security.c | 1 -
> > 1 file changed, 1 deletion(-)
>
> Merged into lsm/dev-staging, thanks!
Welcome!
Could you please also rebase lsm/dev-staging, to move ab3888c7198d
("LSM: wireup Linux Security Module syscalls") after f7875966dc0c
("tools headers UAPI: Sync files changed by new fchmodat2 and
map_shadow_stack syscalls with the kernel sources")?
Thanks
Roberto
Powered by blists - more mailing lists