Received-SPF: pass (google.com: domain of linux-kernel+bounces-144758-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.48.161 as permitted sender) client-ip=147.75.48.161;
Content-Type: text/plain;
	charset=us-ascii
Precedence: bulk
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.500.171.1.1\))
Subject: Re: [kpsingh:static_calls] [security]  9e15595ed0:
 Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots
From: KP Singh <kpsingh@kernel.org>
In-Reply-To: <202404151225.ce542e38-lkp@intel.com>
Date: Mon, 15 Apr 2024 10:26:39 +0200
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
Content-Transfer-Encoding: quoted-printable
Message-Id: <757538DA-07A4-4332-BAFA-B864BFD06A76@kernel.org>
References: <202404151225.ce542e38-lkp@intel.com>
To: kernel test robot <oliver.sang@intel.com>


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

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


>=20
> 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
>=20
>=20
> [    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=3Dcapability,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)=20
> [ 1.028948][ T0] ? vprintk =
(kbuild/src/consumer/kernel/printk/printk_safe.c:?)

[...]