From: "Marek Behún" <kabel@kernel.org>
To: Petr Mladek <pmladek@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
John Ogness <john.ogness@linutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Jan Kara <jack@suse.cz>, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] printk/console: Enable console kthreads only when there is no boot console left
Date: Mon, 20 Jun 2022 20:38:36 +0200 [thread overview]
Message-ID: <20220620203836.0f323667@thinkpad> (raw)
In-Reply-To: <YrCO04oNncE1xF5K@alley>
On Mon, 20 Jun 2022 17:14:27 +0200
Petr Mladek <pmladek@suse.com> wrote:
> The console kthreads uncovered several races in console drivers.
> All problems were in situation when a console was being properly
> initialized and registered while an early console, using the same
> port, was being used.
>
> These problems are pretty hard to debug because they often result
> into silent boot crashes. It would be nice to fix them but it
> looks like a can of worms.
>
> Prevent these problems by delaying the use of console kthreads
> after all early consoles are gone. It might later be optimized.
> But let's close this can of worms with a big hammer for now
> so that they do not break first impression on the kthreads
> that solve other real problems.
>
> Link: https://lore.kernel.org/r/20220619204949.50d9154d@thinkpad
> Link: https://lore.kernel.org/r/2a82eae7-a256-f70c-fd82-4e510750906e@samsung.com
> Reported=by: Marek Behún <kabel@kernel.org>
> Signed-off-by: Petr Mladek <pmladek@suse.com>
This solves the issue. You have a typo in the reported-by tag
('=' instead of '-').
Tested-by: Marek Behún <kabel@kernel.org>
next prev parent reply other threads:[~2022-06-20 18:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 18:49 Boot stall regression from "printk for 5.19" merge Marek Behún
2022-06-19 22:23 ` John Ogness
2022-06-19 22:31 ` John Ogness
2022-06-20 10:02 ` Marek Behún
2022-06-20 9:29 ` Marek Behún
2022-06-20 11:44 ` Petr Mladek
2022-06-20 11:47 ` Petr Mladek
2022-06-20 12:04 ` Ilpo Järvinen
2022-06-20 13:48 ` Linus Torvalds
2022-06-20 14:24 ` Petr Mladek
2022-06-20 15:14 ` [PATCH] printk/console: Enable console kthreads only when there is no boot console left Petr Mladek
2022-06-20 15:16 ` Petr Mladek
2022-06-20 18:38 ` Marek Behún [this message]
2022-06-20 19:10 ` Linus Torvalds
2022-06-20 22:25 ` Petr Mladek
2022-06-20 22:51 ` John Ogness
2022-06-24 22:41 ` Steven Rostedt
2022-06-29 8:29 ` Petr Mladek
2022-06-20 5:23 ` Boot stall regression from "printk for 5.19" merge Sergey Senozhatsky
2022-06-20 10:02 ` Marek Behún
2022-06-20 10:13 ` Sergey Senozhatsky
2022-06-20 10:29 ` Marek Behún
2022-06-20 11:01 ` Andy Shevchenko
2022-06-20 10:38 ` Daniel Palmer
2022-06-21 9:39 ` Thorsten Leemhuis
2022-07-04 9:32 ` Boot stall regression from "printk for 5.19" merge #forregzbot Thorsten Leemhuis
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=20220620203836.0f323667@thinkpad \
--to=kabel@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jack@suse.cz \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).