From: Petr Mladek <pmladek@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: [GIT PULL] printk for 5.8
Date: Fri, 12 Jun 2020 10:40:49 +0200 [thread overview]
Message-ID: <20200612084049.GC4311@linux-b0ei> (raw)
Linus,
please pull one more printk fix from
git://git.kernel.org/pub/scm/linux/kernel/git/printk/linux tags/printk-for-5.8-kdb-nmi
==========================
+ Make sure that messages printed from KDB context are redirected to KDB
console handlers. It did not work when KDB interrupted NMI or printk_safe
contexts.
===========================
Arm people started hitting this problem more often recently. I forgot
to add the fix into the previous pull request by mistake.
----------------------------------------------------------------
Petr Mladek (1):
printk/kdb: Redirect printk messages into kdb in any context
kernel/printk/printk.c | 14 +-------------
kernel/printk/printk_safe.c | 7 +++++++
2 files changed, 8 insertions(+), 13 deletions(-)
next reply other threads:[~2020-06-12 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 8:40 Petr Mladek [this message]
2020-06-12 19:25 ` [GIT PULL] printk for 5.8 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-06-01 11:47 Petr Mladek
2020-06-01 19:35 ` pr-tracker-bot
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=20200612084049.GC4311@linux-b0ei \
--to=pmladek@suse.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel.thompson@linaro.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.