diff options
| author | Petr Mladek <pmladek@suse.com> | 2022-06-23 16:51:55 +0200 |
|---|---|---|
| committer | Petr Mladek <pmladek@suse.com> | 2022-06-23 18:41:40 +0200 |
| commit | 2d9ef940f89e0ab4fde7ba6f769d82f2a450c35a (patch) | |
| tree | 90be8f440be84f10b095d6aac0dd486d72b47919 /kernel/reboot.c | |
| parent | 007eeab7e9f03a3108c300c03e11a6c151e430c9 (diff) | |
Revert "printk: extend console_lock for per-console locking"
This reverts commit 8e274732115f63c1d09136284431b3555bd5cc56.
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-5-pmladek@suse.com
Diffstat (limited to 'kernel/reboot.c')
0 files changed, 0 insertions, 0 deletions