[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <YqybK+kFriV9yeIx@alley>
Date: Fri, 17 Jun 2022 17:18:03 +0200
From: Petr Mladek <pmladek@...e.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>,
Steven Rostedt <rostedt@...dmis.org>,
John Ogness <john.ogness@...utronix.de>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Jan Kara <jack@...e.cz>, Peter Zijlstra <peterz@...radead.org>,
"Paul E. McKenney" <paulmck@...nel.org>,
Peter Geis <pgwipeout@...il.com>, linux-kernel@...r.kernel.org
Subject: [GIT PULL] printk fixups for 5.19-rc3
Hi Linus,
please pull two printk fixups from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux.git tags/printk-for-5.19-rc3
=============================
- Make the global console_sem available for CPU that is handling
panic() or shutdown. It is an old problem when an existing
console lock owner might block console output. It became
more visible with the kthreads.
=============================
I am sorry for the late pull request. I wanted to give it at
least two days in linux-next.
----------------------------------------------------------------
Petr Mladek (3):
printk: Block console kthreads when direct printing will be required
printk: Wait for the global console lock when the system is going down
Merge branch 'rework/kthreads' into for-linus
include/linux/printk.h | 5 +++++
kernel/panic.c | 2 ++
kernel/printk/internal.h | 2 ++
kernel/printk/printk.c | 8 +++++++-
kernel/printk/printk_safe.c | 32 ++++++++++++++++++++++++++++++++
kernel/reboot.c | 2 ++
6 files changed, 50 insertions(+), 1 deletion(-)
Powered by blists - more mailing lists