linux-kernel - Re: [PATCH] rv: Fix boot failure when kernel lockdown is active

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wm5x18bf.fsf@yellow.woof>
Date: Wed, 17 Sep 2025 16:07:32 +0200
From: Nam Cao <namcao@...utronix.de>
To: Gabriele Monaco <gmonaco@...hat.com>, Xiu Jianfeng
 <xiujianfeng@...weicloud.com>, rostedt@...dmis.org, mhiramat@...nel.org
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org,
 nicolas.bouchinet@....cyber.gouv.fr, xiujianfeng@...wei.com
Subject: Re: [PATCH] rv: Fix boot failure when kernel lockdown is active

Gabriele Monaco <gmonaco@...hat.com> writes:
> On Wed, 2025-09-17 at 12:57 +0000, Xiu Jianfeng wrote:
>> From: Xiu Jianfeng <xiujianfeng@...wei.com>
>> 
>> When booting kernel with lockdown=confidentiality parameter, the
>> system
>> will hang at rv_register_reactor() due to waiting for
>> rv_interface_lock,
>> as shown in the following log,
>> 
>
> Thanks for finding this, the problem was already fixed in [1], which is
> on its way to getting merged.
>
> [1] -
> https://lore.kernel.org/all/20250903065112.1878330-1-zhen.ni@easystack.cn

Yeah, but it is interesting that this is causing real boot problem. I
thought that commit merely fixes a theoretical bug. I guess this is an
even stronger motivation to use lock guards.

Nam