linux-kernel - Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack traces

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]

Date:   Tue, 23 Feb 2021 12:57:39 +0100
From:   Vlastimil Babka <vbabka@...e.cz>
To:     Thorsten Leemhuis <linux@...mhuis.info>,
        Jonathan Corbet <corbet@....net>,
        Randy Dunlap <rdunlap@...radead.org>
Cc:     linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
        Sasha Levin <sashal@...nel.org>,
        Joerg Roedel <joro@...tes.org>,
        Qais Yousef <qais.yousef@....com>,
        Damian Tometzki <linux@...etzki.de>
Subject: Re: [PATCH] docs: reporting-issues.rst: explain how to decode stack
 traces

On 2/15/21 6:28 PM, Thorsten Leemhuis wrote:
> Replace placeholder text about decoding stack traces with a section that
> properly describes what a typical user should do these days. To make
> it works for them, add a paragraph in an earlier section to ensure
> people build their kernels with everything that's needed to decode stack
> traces later.

Looks good!

> Signed-off-by: Thorsten Leemhuis <linux@...mhuis.info>
> Reviewed-by: Qais Yousef <qais.yousef@....com>

Acked-by: Vlastimil Babka <vbabka@...e.cz>

Thanks!