linux-kernel - Re: [PATCH] pstore: Add prefix to ECC messages

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: <164616027128.2800203.5940158670244885252.b4-ty@chromium.org>
Date:   Tue,  1 Mar 2022 10:44:35 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Anton Vorontsov <anton@...msg.org>,
        Tony Luck <tony.luck@...el.com>,
        Colin Cross <ccross@...roid.com>,
        Vincent Whitchurch <vincent.whitchurch@...s.com>
Cc:     Kees Cook <keescook@...omium.org>, kernel@...s.com,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] pstore: Add prefix to ECC messages

On Tue, 1 Mar 2022 15:49:32 +0100, Vincent Whitchurch wrote:
> The "No errors detected" message from the ECC code is shown at the end
> of the pstore log and can be confusing or misleading, especially since
> it usually appears just after a kernel crash log which normally means
> quite the opposite of "no errors".  Prefix the message to clarify that
> this message is only about ECC-detected errors.
> 
> 
> [...]

Excellent point. :)

Applied to for-next/pstore, thanks!

[1/1] pstore: Add prefix to ECC messages
      https://git.kernel.org/kees/c/023bbde3db41

-- 
Kees Cook