linux-kernel - Re: [PATCH v2] RAS: Report ARM processor information to userspace

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: <BB2F2992-E9FB-435D-B33C-2334E3D9F3D3@alien8.de>
Date:   Wed, 26 Jan 2022 10:54:11 +0000
From:   Boris Petkov <bp@...en8.de>
To:     linux-kernel@...r.kernel.org, linux-edac@...r.kernel.org,
        tony.luck@...el.com
Subject: Re: [PATCH v2] RAS: Report ARM processor information to userspace

On January 26, 2022 3:09:06 AM UTC, lostway@....edu.cn wrote:
>From: Shengwei Luo <luoshengwei@...wei.com>
>
>The ARM processor error section includes several ARM processor error
>information, several ARM processor context information and several
>vendor specific error information structures. In addition to these
>info, there are error severity and cpu logical index about the event.
>Report all of these information to userspace via perf i/f.

 A patch commit message needs to explain why a change is being done, not what is being done. The "what" I can see most of the time.

-- 
Sent from a small device: formatting sux and brevity is inevitable.