All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Ogness <john.ogness@linutronix.de>
To: Vlastimil Babka <vbabka@suse.cz>,
	Pierre Gondois <pierre.gondois@arm.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users@vger.kernel.org,
	Steven Rostedt <rostedt@goodmis.org>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [ANNOUNCE] v6.3-rc2-rt3
Date: Fri, 14 Apr 2023 17:07:25 +0206	[thread overview]
Message-ID: <87pm86ece2.fsf@jogness.linutronix.de> (raw)
In-Reply-To: <73b5657a-4c47-980a-e709-cd6a880c067c@suse.cz>

On 2023-04-14, Vlastimil Babka <vbabka@suse.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

  reply	other threads:[~2023-04-14 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-14 17:05 [ANNOUNCE] v6.3-rc2-rt3 Sebastian Andrzej Siewior
2023-03-14 17:12 ` Sebastian Andrzej Siewior
2023-04-14 11:55   ` Pierre Gondois
2023-04-14 13:49     ` John Ogness
2023-04-14 13:56       ` Vlastimil Babka
2023-04-14 15:01         ` John Ogness [this message]
2023-04-14 15:38           ` Vlastimil Babka
2023-04-18 15:08             ` Sebastian Andrzej Siewior

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=87pm86ece2.fsf@jogness.linutronix.de \
    --to=john.ogness@linutronix.de \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=pierre.gondois@arm.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.