From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
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>,
Peter Zijlstra <peterz@infradead.org>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
linux-kernel@vger.kernel.org, "4 . 13+" <stable@vger.kernel.org>
Subject: Re: [PATCH] printk/nmi: Prevent deadlock when serializing NMI backtraces
Date: Tue, 19 Jun 2018 17:27:16 +0900 [thread overview]
Message-ID: <20180619082716.GD405@jagdpanzerIV> (raw)
In-Reply-To: <20180619075219.iq7ztwu43bn4uua7@pathway.suse.cz>
On (06/19/18 09:52), Petr Mladek wrote:
> On Mon 2018-06-18 19:07:18, Sergey Senozhatsky wrote:
> > On (06/18/18 11:39), Petr Mladek wrote:
> > [..]
> >
> > Hmm. Can't answer right now :)
>
> Please, let me know what name you would like ;-)
:) Wow, it's hard. Maybe we can derive some bits from the ftrace_dump()
function name? Dunno... Does printk_dump_nmi_enter() sound terrible?
Maybe Steven has some opinions on this?
-ss
next prev parent reply other threads:[~2018-06-19 8:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 14:39 [PATCH] printk/nmi: Prevent deadlock when serializing NMI backtraces Petr Mladek
2018-05-18 2:07 ` Sergey Senozhatsky
2018-05-18 6:38 ` Sergey Senozhatsky
2018-05-18 8:10 ` Petr Mladek
2018-05-22 21:43 ` Steven Rostedt
2018-05-23 2:01 ` Sergey Senozhatsky
2018-05-28 12:27 ` Petr Mladek
2018-06-05 12:47 ` Petr Mladek
2018-06-06 5:10 ` Sergey Senozhatsky
2018-06-06 10:33 ` Sergey Senozhatsky
2018-06-08 10:48 ` Petr Mladek
2018-06-18 6:37 ` Sergey Senozhatsky
2018-06-18 9:39 ` Petr Mladek
2018-06-18 10:07 ` Sergey Senozhatsky
2018-06-19 7:52 ` Petr Mladek
2018-06-19 8:27 ` Sergey Senozhatsky [this message]
2018-06-19 13:23 ` Steven Rostedt
2018-06-20 1:58 ` Sergey Senozhatsky
2018-06-20 2:32 ` Steven Rostedt
2018-06-20 4:17 ` Sergey Senozhatsky
2018-06-06 11:15 ` Petr Mladek
2018-06-07 5:40 ` Sergey Senozhatsky
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=20180619082716.GD405@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=stable@vger.kernel.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 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).