[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4e8bae6a0ada1d52893381e7542220973f0367fb.camel@redhat.com>
Date: Thu, 18 Sep 2025 10:36:21 +0200
From: Gabriele Monaco <gmonaco@...hat.com>
To: Nam Cao <namcao@...utronix.de>
Cc: 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
On Wed, 2025-09-17 at 16:07 +0200, Nam Cao wrote:
> 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.
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.
But I agree, that's something we may want to do sooner than later.
I'm currently not refactoring the RV core so I won't be touching that
for a while, but any patch is more than welcome!
Gabriele
Powered by blists - more mailing lists