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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <CAP4=nvQubUmOVivgzOtYRhMmZaq75WRmRdBnsn0HYJfHHZhzmw@mail.gmail.com>
Date: Thu, 18 Sep 2025 11:48:20 +0200
From: Tomas Glozar <tglozar@...hat.com>
To: Gabriele Monaco <gmonaco@...hat.com>
Cc: Nam Cao <namcao@...utronix.de>, linux-trace-kernel@...r.kernel.org, 
	linux-kernel@...r.kernel.org, nicolas.bouchinet@....cyber.gouv.fr, 
	Xiu Jianfeng <xiujianfeng@...weicloud.com>, rostedt@...dmis.org, mhiramat@...nel.org
Subject: Re: [PATCH] rv: Fix boot failure when kernel lockdown is active

čt 18. 9. 2025 v 10:36 odesílatel Gabriele Monaco <gmonaco@...hat.com> napsal:
>
> Yeah totally, I have the feeling that with the kernel there's no such a
> thing as a "theoretical bug", kinda like a good consequence of Murphy's
> Law.
>

My understanding of "theoretical bug" is that it's code that is
semantically equivalent to a bug-free code, but becomes buggy after
doing an "innocent" change. The bug might be more or less
"theoretical" based on how "innocent" that change is. Of course, in a
codebase of the size of a Linux kernel, this tends to happen quite
often, and is not always possible to get rid of completely...

Tomas