[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pm86ece2.fsf@jogness.linutronix.de>
Date: Fri, 14 Apr 2023 17:07:25 +0206
From: John Ogness <john.ogness@...utronix.de>
To: Vlastimil Babka <vbabka@...e.cz>,
Pierre Gondois <pierre.gondois@....com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: LKML <linux-kernel@...r.kernel.org>,
linux-rt-users@...r.kernel.org,
Steven Rostedt <rostedt@...dmis.org>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [ANNOUNCE] v6.3-rc2-rt3
On 2023-04-14, Vlastimil Babka <vbabka@...e.cz> wrote:
> Is it perhaps a similar situation to this thread?
>
> https://lore.kernel.org/all/20230412124735.GE628377@hirez.programming.kicks-ass.net/
We are dealing with a spin_lock() inside a raw_spin_lock() section. The
legacy console drivers do this. The fix is the new atomic/threaded
consoles. For CONFIG_PREEMPT_RT a workaround is implemented so that the
legacy consoles avoid this. For !CONFIG_PREEMPT_RT you can expect
CONFIG_PROVE_RAW_LOCK_NESTING to cause a splat on that printk().
Or perhaps that particular printk() in cblist_init_generic() should be
changed to printk_deferred() as a temporary whack-a-mole
workaround.
John Ogness
Powered by blists - more mailing lists