Commit 05c96b37 authored by Petr Mladek's avatar Petr Mladek

Revert "printk: Block console kthreads when direct printing will be required"

This reverts commit c3230283.

The testing of 5.19 release candidates revealed missing synchronization
between early and regular console functionality.

It would be possible to start the console kthreads later as a workaround.
But it is clear that console lock serialized console drivers between
each other. It opens a big area of possible problems that were not
considered by people involved in the development and review.

printk() is crucial for debugging kernel issues and console output is
very important part of it. The number of consoles is huge and a proper
review would take some time. As a result it need to be reverted for 5.19.

Link: https://lore.kernel.org/r/YrBdjVwBOVgLfHyb@alleySigned-off-by: default avatarPetr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20220623145157.21938-3-pmladek@suse.com
parent 20fb0c82
...@@ -3729,9 +3729,7 @@ static bool printer_should_wake(struct console *con, u64 seq) ...@@ -3729,9 +3729,7 @@ static bool printer_should_wake(struct console *con, u64 seq)
return true; return true;
if (con->blocked || if (con->blocked ||
console_kthreads_atomically_blocked() || console_kthreads_atomically_blocked()) {
system_state > SYSTEM_RUNNING ||
oops_in_progress) {
return false; return false;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment