Messages in this thread | | | Date | Tue, 19 Jun 2018 09:23:04 -0400 | From | Steven Rostedt <> | Subject | Re: [PATCH] printk/nmi: Prevent deadlock when serializing NMI backtraces |
| |
On Tue, 19 Jun 2018 17:27:16 +0900 Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com> wrote:
> 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? >
What exactly is the question?
Also, from a previous email in this thread, if you have to risk interleaved output to solve a deadlock, then just do that.
-- Steve
| |