From: Roberto Sassu <roberto.sassu@huaweicloud.com>
To: Paul Moore <paul@paul-moore.com>, jmorris@namei.org, serge@hallyn.com
Cc: linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, zohar@linux.ibm.com,
linux-integrity@vger.kernel.org,
Roberto Sassu <roberto.sassu@huawei.com>
Subject: Re: [PATCH] security: Don't yet account for IMA in LSM_CONFIG_COUNT calculation
Date: Thu, 26 Oct 2023 17:12:03 +0200 [thread overview]
Message-ID: <447298d65b497fb1a7f8d47c4f1a3137eba24511.camel@huaweicloud.com> (raw)
In-Reply-To: <dd0f6611c7b46f3cecee2b84681c45b1.paul@paul-moore.com>
On Thu, 2023-10-26 at 10:48 -0400, Paul Moore wrote:
> On Oct 26, 2023 Roberto Sassu <roberto.sassu@huaweicloud.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@huawei.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
next prev parent reply other threads:[~2023-10-26 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 9:02 [PATCH] security: Don't yet account for IMA in LSM_CONFIG_COUNT calculation Roberto Sassu
2023-10-26 14:48 ` Paul Moore
2023-10-26 15:12 ` Roberto Sassu [this message]
2023-10-26 15:59 ` Paul Moore
2023-10-26 16:36 ` Paul Moore
2023-11-13 4:06 ` Paul Moore
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=447298d65b497fb1a7f8d47c4f1a3137eba24511.camel@huaweicloud.com \
--to=roberto.sassu@huaweicloud.com \
--cc=jmorris@namei.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=roberto.sassu@huawei.com \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox