From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Dmitry Safonov <0x7f454c46@gmail.com>,
Valentin Schneider <valentin.schneider@arm.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephen Boyd <swboyd@chromium.org>,
Alexander Potapenko <glider@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>
Subject: [PATCH next v1 0/2] introduce printk cpu lock
Date: Mon, 31 May 2021 18:20:49 +0200 [thread overview]
Message-ID: <20210531162051.2325-1-john.ogness@linutronix.de> (raw)
While working on removing the safe buffers for printk [0] we
stumbled on a cpu-reentrant spinning lock used by dump_stack(). This
type of lock (dubbed a cpu lock) will cause deadlock risks once we
introduce atomic consoles because atomic consoles also need such a
lock.
Although we are not yet ready to introduce atomic consoles, this is
an appropriate time to provide an official cpu lock to be used for
all things relating to printk (including the atomic consoles, once
they are introduced).
This series also extends the new printk cpu lock to cover
show_regs().
This series is against next-20210528.
John Ogness
[0] https://lore.kernel.org/lkml/YGW63%2FelFr%2FgYW1u@alley
John Ogness (2):
dump_stack: move cpu lock to printk.c
nmi_backtrace: use the printk cpu lock for show_regs()
include/linux/printk.h | 13 ++++++
kernel/printk/printk.c | 92 ++++++++++++++++++++++++++++++++++++++++++
lib/dump_stack.c | 43 ++------------------
lib/nmi_backtrace.c | 4 ++
4 files changed, 112 insertions(+), 40 deletions(-)
--
2.20.1
next reply other threads:[~2021-05-31 17:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 16:20 John Ogness [this message]
2021-05-31 16:20 ` [PATCH next v1 1/2] dump_stack: move cpu lock to printk.c John Ogness
2021-05-31 16:30 ` John Ogness
2021-05-31 20:04 ` kernel test robot
2021-05-31 21:49 ` kernel test robot
2021-06-01 2:55 ` Sergey Senozhatsky
2021-06-01 6:58 ` John Ogness
2021-06-01 7:37 ` John Ogness
2021-06-01 13:29 ` Petr Mladek
2021-06-01 13:59 ` Petr Mladek
2021-06-01 14:21 ` John Ogness
2021-06-03 6:33 ` Petr Mladek
2021-05-31 16:20 ` [PATCH next v1 2/2] nmi_backtrace: use the printk cpu lock for show_regs() John Ogness
2021-06-01 14:25 ` Petr Mladek
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=20210531162051.2325-1-john.ogness@linutronix.de \
--to=john.ogness@linutronix.de \
--cc=0x7f454c46@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=glider@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=swboyd@chromium.org \
--cc=tglx@linutronix.de \
--cc=valentin.schneider@arm.com \
/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).