linux-kernel - Re: [PATCH] printk/nmi: Prevent deadlock when serializing NMI backtraces

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180619092304.6b6ba390@gandalf.local.home>
Date:   Tue, 19 Jun 2018 09:23:04 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Cc:     Petr Mladek <pmladek@...e.com>,
        Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>,
        linux-kernel@...r.kernel.org, "4 . 13+" <stable@...r.kernel.org>
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@...il.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