From: Guenter Roeck <linux@roeck-us.net>
To: KP Singh <kpsingh@kernel.org>,
linux-security-module@vger.kernel.org, bpf@vger.kernel.org
Cc: ast@kernel.org, paul@paul-moore.com, casey@schaufler-ca.com,
andrii@kernel.org, keescook@chromium.org, daniel@iogearbox.net,
renauld@google.com, revest@chromium.org, song@kernel.org
Subject: Re: [PATCH v15 0/4] Reduce overhead of LSMs with static calls
Date: Fri, 16 Aug 2024 14:30:43 -0700 [thread overview]
Message-ID: <d95d9cbe-54ea-4e85-aa63-4494508be5e7@roeck-us.net> (raw)
In-Reply-To: <20240816154307.3031838-1-kpsingh@kernel.org>
On 8/16/24 08:43, KP Singh wrote:
[ ... ]
> # v14 to v15
>
> * Fixed early LSM init wuth Patch 1
> * Made the static call table aligned to u64 and added a comment as to why this
> is needed.
>
Applied to v6.11-rc3, together with several other LSM patches from linux-next
to avoid conflicts, this series passes all my qemu tests. Feel free to add
Tested-by: Guenter Roeck <linux@roeck-us.net>
Thanks,
Guenter
next prev parent reply other threads:[~2024-08-16 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 15:43 [PATCH v15 0/4] Reduce overhead of LSMs with static calls KP Singh
2024-08-16 15:43 ` [PATCH v15 1/4] init/main.c: Initialize early LSMs after arch code, static keys and calls KP Singh
2024-08-16 15:43 ` [PATCH v15 2/4] kernel: Add helper macros for loop unrolling KP Singh
2024-08-16 15:43 ` [PATCH v15 3/4] lsm: count the LSMs enabled at compile time KP Singh
2024-08-20 4:39 ` Paul Moore
2024-08-22 16:27 ` Paul Moore
2025-11-26 17:14 ` Andy Shevchenko
2025-11-26 19:02 ` Paul Moore
2025-11-26 19:44 ` Andy Shevchenko
2024-08-16 15:43 ` [PATCH v15 4/4] lsm: replace indirect LSM hook calls with static calls KP Singh
2024-08-16 21:30 ` Guenter Roeck [this message]
2024-08-20 4:33 ` [PATCH v15 0/4] Reduce overhead of LSMs " Paul Moore
2024-08-18 4:37 ` Tetsuo Handa
2024-08-20 5:17 ` 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=d95d9cbe-54ea-4e85-aa63-4494508be5e7@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=daniel@iogearbox.net \
--cc=keescook@chromium.org \
--cc=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=renauld@google.com \
--cc=revest@chromium.org \
--cc=song@kernel.org \
/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