linux-kernel - Re: [PATCH] x86/microcode: Be more verbose, especially about loading errors

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: <20231206195814.GDZXDSVgtCWspEJx8Q@fat_crate.local>
Date:   Wed, 6 Dec 2023 20:58:14 +0100
From:   Borislav Petkov <bp@...en8.de>
To:     Jann Horn <jannh@...gle.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Ingo Molnar <mingo@...hat.com>,
        Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org,
        "H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86/microcode: Be more verbose, especially about loading
 errors

On Wed, Dec 06, 2023 at 06:28:44PM +0100, Jann Horn wrote:
> The AMD ucode loader contains several checks for corrupted ucode blobs that
> only log with pr_debug(); make them pr_err(), corrupted ucode blobs are
> bad.
> 
> Also make both microcode loaders a bit more verbose about whether they
> found ucode blobs at all and whether they found ucode for the specific CPU.

So far, so good.

The only thing I'm missing here is the *why*.

There's merit in not complaining about corrupted microcode blobs because
they won't be loaded anyway: no harm, no foul.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette