archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <>
To: John Ogness <>
Cc: Linus Torvalds <>,
	Sergey Senozhatsky <>,
	Steven Rostedt <>,
	Andy Shevchenko <>,
	Rasmus Villemoes <>,
	Jan Kara <>, Peter Zijlstra <>,
	Linux Kernel Mailing List <>
Subject: Re: [GIT PULL] printk for 5.19
Date: Thu, 26 May 2022 14:09:25 +0200	[thread overview]
Message-ID: <Yo9t9Vg/DpvMqCs7@alley> (raw)
In-Reply-To: <>

On Thu 2022-05-26 00:08:46, John Ogness wrote:
> On 2022-05-25, Linus Torvalds <> wrote:
> > On Mon, May 23, 2022 at 6:21 AM Petr Mladek <> wrote:
> >> There are situations when the kthreads are either not available or
> >> not reliable, for example, early boot, suspend, or panic. In these
> >> situations, printk() uses the legacy mode and tries to handle
> >> consoles immediately.
> >
> > Looking through the commits, I don't see how that "printk: wake up all
> > waiters" makes any sense at all.
> >
> > It *ALREADY* woke up all waiters as far as I can see.
> >
> > Doing a wake_up_interruptible() will stop waking things up only when
> > it hits a *exclusive* waiter, and as far as I can tell, there are no
> > exclusive waiters there.
> You are correct. @log_wait never has exclusive waiters. I will post a
> patch to revert the change in question.

John, Yes, please do so.

> > But when I see something really core like printk() get confused and
> > mis-understand basic wait queue behavior, that makes me go "This is
> > WRONG".

Linus, thanks a lot for catching and explaining the problem.

Yeah, it is a shame. I have met code with exclusive waiters only once,
8 years ago and completely forgot about it. I was curious how it
worked with more log waiters but I put it into TODO list. The new
code looked safe and I was too focused on finding potential problems.

Best Regards,

  reply	other threads:[~2022-05-26 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 13:21 [GIT PULL] printk for 5.19 Petr Mladek
2022-05-25 18:09 ` Linus Torvalds
2022-05-25 22:02   ` John Ogness
2022-05-26 12:09     ` Petr Mladek [this message]
2022-05-26 17:13       ` Linus Torvalds
2022-05-25 18:37 ` pr-tracker-bot

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Yo9t9Vg/DpvMqCs7@alley \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).