linux-kernel - Re: [PATCH] panic: Add sysctl/cmdline to dump all CPUs backtraces on oops event

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] [day] [month] [year] [list]

Message-ID: <a4f5bff0-82c8-114e-0386-9d44baa3cfac@canonical.com>
Date:   Mon, 16 Mar 2020 10:51:22 -0300
From:   "Guilherme G. Piccoli" <gpiccoli@...onical.com>
To:     Randy Dunlap <rdunlap@...radead.org>,
        Matthew Wilcox <willy@...radead.org>
Cc:     linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
        mcgrof@...nel.org, keescook@...omium.org, yzaikin@...gle.com,
        tglx@...utronix.de, akpm@...ux-foundation.org, kernel@...ccoli.net
Subject: Re: [PATCH] panic: Add sysctl/cmdline to dump all CPUs backtraces on
 oops event

On 14/03/2020 18:18, Randy Dunlap wrote:
> On 3/14/20 7:28 AM, Matthew Wilcox wrote:
>> On Tue, Mar 10, 2020 at 01:59:15PM -0700, Randy Dunlap wrote:
>>>> +oops_all_cpu_backtrace:
>>>> +================
>>>> +
>>>> +Determines if kernel should NMI all CPUs to dump their backtraces when
>>>
>>> I would much prefer that to be written without using NMI as a verb.
>>
>> Concrete suggestion: "If this option is set, the kernel will send an NMI to
>> all CPUs to dump ..."
>>
> 
> Ack.  Thanks for that.
> 

Thanks Randy and Matthew! I'll implement those changes and resend as V2.
If anybody has suggestions of people I should add to CC list, please let
me know.

Thanks again,


Guilherme