Revert "printk: remove @console_locked"
authorPetr Mladek <pmladek@suse.com>
Thu, 23 Jun 2022 14:51:54 +0000 (16:51 +0200)
committerPetr Mladek <pmladek@suse.com>
Thu, 23 Jun 2022 16:41:40 +0000 (18:41 +0200)
commit007eeab7e9f03a3108c300c03e11a6c151e430c9
tree3af2e5a5c2ed39a4232bdf901ea7beaeb0fc7121
parent05c96b3713aa2a406d0c4ef0505bf80a6748fedb
Revert "printk: remove @console_locked"

This reverts commit ab406816fca009349b89cbde885daf68a8c77e33.

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@alley
Signed-off-by: Petr Mladek <pmladek@suse.com>
Link: https://lore.kernel.org/r/20220623145157.21938-4-pmladek@suse.com
kernel/printk/printk.c