public inbox for linux-security-module@vger.kernel.org
 help / color / mirror / Atom feed
From: KP Singh <kpsingh@kernel.org>
To: kernel test robot <oliver.sang@intel.com>
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>,
	Andrii Nakryiko <andrii@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-security-module@vger.kernel.org
Subject: Re: [kpsingh:static_calls] [security]  9e15595ed0: Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots
Date: Mon, 15 Apr 2024 10:26:39 +0200	[thread overview]
Message-ID: <757538DA-07A4-4332-BAFA-B864BFD06A76@kernel.org> (raw)
In-Reply-To: <202404151225.ce542e38-lkp@intel.com>



> On 15 Apr 2024, at 07:30, kernel test robot <oliver.sang@intel.com> wrote:
> 
> 
> 
> Hello,
> 
> kernel test robot noticed "Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots" on:
> 
> commit: 9e15595ed016dc9b726b7b13ec3d9b92b9e53c68 ("security: Replace indirect LSM hook calls with static calls")
> https://git.kernel.org/cgit/linux/kernel/git/kpsingh/linux.git static_calls
> 
> in testcase: boot
> 
> compiler: clang-17
> test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
> 
> (please refer to attached dmesg/kmsg for entire log/backtrace)
> 
> 
> +-----------------------------------------------------------------------+------------+------------+
> |                                                                       | e2f2a7e74d | 9e15595ed0 |
> +-----------------------------------------------------------------------+------------+------------+
> | Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots | 0          | 12         |
> +-----------------------------------------------------------------------+------------+------------+
> 

This seems like an odd config which does not enable STATIC_CALL, I am going to make CONFIG_SECURITY depend on CONFIG_STATIC_CALL and make the dependency explicit.

- KP



> 
> 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 <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-lkp/202404151225.ce542e38-lkp@intel.com
> 
> 
> [    1.020355][    T0] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
> [    1.020966][    T0] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format.
> [    1.022632][    T0] Freeing SMP alternatives memory: 32K
> [    1.023145][    T0] pid_max: default: 32768 minimum: 301
> [    1.025772][    T0] LSM: initializing lsm=capability,ima
> [    1.027282][    T0] Kernel panic - not syncing: lsm_static_call_init - Ran out of static slots.
> [    1.028283][    T0] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G                T  6.9.0-rc1-00003-g9e15595ed016 #1
> [    1.028948][    T0] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.2-debian-1.16.2-1 04/01/2014
> [    1.028948][    T0] Call Trace:
> [ 1.028948][ T0] dump_stack_lvl (kbuild/src/consumer/lib/dump_stack.c:116) 
> [ 1.028948][ T0] ? vprintk (kbuild/src/consumer/kernel/printk/printk_safe.c:?)

[...]


  reply	other threads:[~2024-04-15  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-15  5:30 [kpsingh:static_calls] [security] 9e15595ed0: Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots kernel test robot
2024-04-15  8:26 ` KP Singh [this message]
2024-04-15 13:04   ` Tetsuo Handa
2024-04-15 14:23     ` Paul Moore
     [not found]       ` <CACYkzJ4G7hO0DNSBy4wpJG1PSgNkifuYcfOeTTpyVBtBtWvQSg@mail.gmail.com>
2024-04-15 15:47         ` KP Singh
2024-04-15 20:42           ` KP Singh
2024-04-15 20:54             ` Casey Schaufler
2024-04-15 21:39               ` KP Singh

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=757538DA-07A4-4332-BAFA-B864BFD06A76@kernel.org \
    --to=kpsingh@kernel.org \
    --cc=andrii@kernel.org \
    --cc=casey@schaufler-ca.com \
    --cc=keescook@chromium.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=oliver.sang@intel.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