From: Kees Cook <keescook@chromium.org>
To: KP Singh <kpsingh@kernel.org>
Cc: linux-security-module@vger.kernel.org, bpf@vger.kernel.org,
paul@paul-moore.com, casey@schaufler-ca.com, song@kernel.org,
daniel@iogearbox.net, ast@kernel.org, renauld@google.com,
pabeni@redhat.com
Subject: Re: [PATCH v7 0/5] Reduce overhead of LSMs with static calls
Date: Sat, 4 Nov 2023 13:45:20 -0700 [thread overview]
Message-ID: <202311041343.03239A8AC1@keescook> (raw)
In-Reply-To: <20231102005521.346983-1-kpsingh@kernel.org>
On Thu, Nov 02, 2023 at 01:55:16AM +0100, KP Singh wrote:
> NOTE: The warning shown by the kernel test bot is spurious, there is no flex array
> and it seems to come from an older tool chain.
>
> https://lore.kernel.org/bpf/202310111711.wLbijitj-lkp@intel.com/
I was finally able to reproduce this and tracked it down. Fix is here:
https://lore.kernel.org/lkml/20231104204334.work.160-kees@kernel.org/
-Kees
--
Kees Cook
prev parent reply other threads:[~2023-11-04 20:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 0:55 [PATCH v7 0/5] Reduce overhead of LSMs with static calls KP Singh
2023-11-02 0:55 ` [PATCH v7 1/5] kernel: Add helper macros for loop unrolling KP Singh
2023-11-02 0:55 ` [PATCH v7 2/5] security: Count the LSMs enabled at compile time KP Singh
2023-11-02 0:55 ` [PATCH v7 3/5] security: Replace indirect LSM hook calls with static calls KP Singh
2023-11-02 7:51 ` kernel test robot
2023-11-02 0:55 ` [PATCH v7 4/5] bpf: Only enable BPF LSM hooks when an LSM program is attached KP Singh
2023-11-02 2:26 ` Andrii Nakryiko
2023-11-10 22:19 ` KP Singh
2023-11-02 0:55 ` [PATCH v7 5/5] security: Add CONFIG_SECURITY_HOOK_LIKELY KP Singh
2023-11-02 2:26 ` [PATCH v7 0/5] Reduce overhead of LSMs with static calls Andrii Nakryiko
2023-11-02 9:42 ` Tetsuo Handa
2023-11-02 10:01 ` KP Singh
2023-11-02 10:30 ` Tetsuo Handa
2023-11-02 10:48 ` KP Singh
2023-11-04 20:45 ` Kees Cook [this message]
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=202311041343.03239A8AC1@keescook \
--to=keescook@chromium.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=casey@schaufler-ca.com \
--cc=daniel@iogearbox.net \
--cc=kpsingh@kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paul@paul-moore.com \
--cc=renauld@google.com \
--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;
as well as URLs for NNTP newsgroup(s).