[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <30876b80-c437-4916-b982-97c1a95c0747@I-love.SAKURA.ne.jp>
Date: Mon, 15 Apr 2024 22:04:31 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: KP Singh <kpsingh@...nel.org>, kernel test robot <oliver.sang@...el.com>
Cc: oe-lkp@...ts.linux.dev, lkp@...el.com,
Casey Schaufler <casey@...aufler-ca.com>,
Kees Cook <keescook@...omium.org>, Song Liu <song@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>, linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org
Subject: Re: [kpsingh:static_calls] [security] 9e15595ed0:
Kernel_panic-not_syncing:lsm_static_call_init-Ran_out_of_static_slots
On 2024/04/15 17:26, KP Singh wrote:
> 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.
If CONFIG_SECURITY depends on CONFIG_STATIC_CALL, architectures which do not
support CONFIG_STATIC_CALL can no longer use LSM ? That sounds a bad dependency.
Powered by blists - more mailing lists