From: kernel test robot <oliver.sang@intel.com>
To: KP Singh <kpsingh@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Casey Schaufler <casey@schaufler-ca.com>,
Kees Cook <keescook@chromium.org>, Song Liu <song@kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-security-module@vger.kernel.org>, <bpf@vger.kernel.org>,
<paul@paul-moore.com>, <daniel@iogearbox.net>, <ast@kernel.org>,
<kpsingh@kernel.org>, <renauld@google.com>,
<oliver.sang@intel.com>
Subject: Re: [PATCH v4 3/5] security: Replace indirect LSM hook calls with static calls
Date: Wed, 27 Sep 2023 13:26:36 +0800 [thread overview]
Message-ID: <202309271206.d7fb60f9-oliver.sang@intel.com> (raw)
In-Reply-To: <20230922145505.4044003-4-kpsingh@kernel.org>
Hello,
kernel test robot noticed "Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots" on:
commit: e75df0d5718c3d39cd53e2459b04806ed8789253 ("[PATCH v4 3/5] security: Replace indirect LSM hook calls with static calls")
url: https://github.com/intel-lab-lkp/linux/commits/KP-Singh/kernel-Add-helper-macros-for-loop-unrolling/20230922-225925
base: https://git.kernel.org/cgit/linux/kernel/git/bpf/bpf-next.git master
patch link: https://lore.kernel.org/all/20230922145505.4044003-4-kpsingh@kernel.org/
patch subject: [PATCH v4 3/5] security: Replace indirect LSM hook calls with static calls
in testcase: boot
compiler: gcc-12
test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202309271206.d7fb60f9-oliver.sang@intel.com
[ 1.002757][ T0] MDS: Vulnerable: Clear CPU buffers attempted, no microcode
[ 1.006940][ T0] MMIO Stale Data: Unknown: No mitigations
[ 1.010166][ T0] x86/fpu: x87 FPU will use FXSAVE
[ 1.012429][ T0] pid_max: default: 32768 minimum: 301
[ 1.014553][ T0] LSM: initializing lsm=capability,integrity
[ 1.016244][ T0] Kernel panic - not syncing: lsm_static_call_init - Ran out of static slots.
[ 1.018151][ T0] CPU: 0 PID: 0 Comm: swapper Not tainted 6.6.0-rc2-00661-ge75df0d5718c-dirty #1
[ 1.018151][ T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
[ 1.018151][ T0] Call Trace:
[ 1.018151][ T0] dump_stack_lvl (??:?)
[ 1.018151][ T0] dump_stack (??:?)
[ 1.018151][ T0] panic (??:?)
[ 1.018151][ T0] security_add_hooks (??:?)
[ 1.018151][ T0] capability_init (commoncap.c:?)
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20230927/202309271206.d7fb60f9-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-09-27 5:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 14:55 [PATCH v4 0/5] Reduce overhead of LSMs with static calls KP Singh
2023-09-22 14:55 ` [PATCH v4 1/5] kernel: Add helper macros for loop unrolling KP Singh
2023-09-22 14:55 ` [PATCH v4 2/5] security: Count the LSMs enabled at compile time KP Singh
2023-09-22 15:50 ` Kees Cook
2023-09-22 16:07 ` KP Singh
2023-09-27 22:37 ` KP Singh
2023-09-22 14:55 ` [PATCH v4 3/5] security: Replace indirect LSM hook calls with static calls KP Singh
2023-09-23 14:52 ` kernel test robot
2023-09-27 5:26 ` kernel test robot [this message]
2023-09-22 14:55 ` [PATCH v4 4/5] bpf: Only enable BPF LSM hooks when an LSM program is attached KP Singh
2023-09-22 14:55 ` [PATCH v4 5/5] security: Add CONFIG_SECURITY_HOOK_LIKELY KP Singh
2023-09-22 15:50 ` Kees Cook
2023-09-22 15:51 ` [PATCH v4 0/5] Reduce overhead of LSMs with static calls Kees Cook
2023-09-22 18:42 ` Mateusz Guzik
2023-09-23 16:16 ` KP Singh
2023-09-23 17:13 ` Mateusz Guzik
2023-09-23 17:15 ` Mateusz Guzik
2023-09-24 2:46 ` Kees Cook
2023-09-25 20:08 ` Mateusz Guzik
2023-09-25 22:02 ` Kees Cook
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=202309271206.d7fb60f9-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--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-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.