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]
Date:   Mon, 15 Feb 2021 06:25:46 +0100
From:   Thorsten Leemhuis <>
To:     Randy Dunlap <>,
        Jonathan Corbet <>
        Sasha Levin <>,
        Vlastimil Babka <>,
        Joerg Roedel <>,
        Qais Yousef <>,
        Damian Tometzki <>
Subject: Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack

Am 11.02.21 um 18:07 schrieb Randy Dunlap:
> Just a couple of small nits (or one that is repeated):


> On 2/9/21 9:48 PM, Thorsten Leemhuis wrote:
>> - * If the failure includes a stack dump, like an Oops does, consider decoding
>> -   it to find the offending line of code.
>> + * If your failure involves a 'panic', 'oops', or 'warning', consider decoding
>> +   the kernel log to find the line of code that trigger the error.
>                                                    triggered
> […] 
> or it could be "code that triggers"... (just not "trigger").

Ahh, yes, you're right of course. Went with the former, many thx for
taking a look and pointing it out!

Ciao, Thorsten

Powered by blists - more mailing lists