The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Nam Cao <namcao@linutronix.de>,
	linux-trace-kernel@vger.kernel.org,
	 linux-kernel@vger.kernel.org,
	nicolas.bouchinet@oss.cyber.gouv.fr,
	Xiu Jianfeng	 <xiujianfeng@huaweicloud.com>,
	rostedt@goodmis.org, mhiramat@kernel.org
Subject: Re: [PATCH] rv: Fix boot failure when kernel lockdown is active
Date: Fri, 19 Sep 2025 10:52:32 +0200	[thread overview]
Message-ID: <e7ed86066c53078ca55c1ec5c47da7b57cf2ffdf.camel@redhat.com> (raw)
In-Reply-To: <CAP4=nvQubUmOVivgzOtYRhMmZaq75WRmRdBnsn0HYJfHHZhzmw@mail.gmail.com>

On Thu, 2025-09-18 at 11:48 +0200, Tomas Glozar wrote:
> čt 18. 9. 2025 v 10:36 odesílatel Gabriele Monaco <gmonaco@redhat.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...

Yeah good point, we are getting philosophical here :) . This wasn't a
theoretical bug then, just something you don't think will really happen (a
failure creating a sysfs directory) ... until it happens.

The fact there is a way to make that function fail on-demand (kernel lockdown),
makes it just more "real". Moral of the story, better get the compiler check
things for you (lock guards).

Anyway the fix is now upstream.

Gabriele


  reply	other threads:[~2025-09-19  8:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-17 12:57 [PATCH] rv: Fix boot failure when kernel lockdown is active Xiu Jianfeng
2025-09-17 13:57 ` Gabriele Monaco
2025-09-17 14:07   ` Nam Cao
2025-09-18  8:36     ` Gabriele Monaco
2025-09-18  9:48       ` Tomas Glozar
2025-09-19  8:52         ` Gabriele Monaco [this message]
2025-09-19  9:03           ` Nam Cao

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=e7ed86066c53078ca55c1ec5c47da7b57cf2ffdf.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=namcao@linutronix.de \
    --cc=nicolas.bouchinet@oss.cyber.gouv.fr \
    --cc=rostedt@goodmis.org \
    --cc=tglozar@redhat.com \
    --cc=xiujianfeng@huaweicloud.com \
    /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