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:   Sat, 11 Nov 2023 14:19:00 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Borislav Petkov <bp@...en8.de>,
        Thomas Gleixner <tglx@...utronix.de>
Cc:     x86-ml <x86@...nel.org>, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] x86/microcode for 6.7

On Fri, 3 Nov 2023 at 04:06, Borislav Petkov <bp@...en8.de> wrote:
>
> I believe this is the last tip branch from the lineup this merge window.
> It has a lot of nice things, it has been tested on everything we have
> access to so it should be good.

Well, I only now looked more closely at dmesg (because I was testing
an entirely unrelated patch of mine), and I see this:

    smpboot: x86: Booting SMP configuration:
    .... node  #0, CPUs:        #1  #2  #3  #4  #5
    microcode: CPU4: new patch_level=0x0830107a
      #6
    microcode: CPU5: new patch_level=0x0830107a
      #7
    microcode: CPU1: new patch_level=0x0830107a
    microcode: CPU2: new patch_level=0x0830107a
    microcode: CPU3: new patch_level=0x0830107a
    microcode: CPU6: new patch_level=0x0830107a
      #8
    ...
      #63
    microcode: CPU62: new patch_level=0x0830107a
    microcode: CPU63: new patch_level=0x0830107a
    smp: Brought up 1 node, 64 CPUs
    ...
    mip6: Mobile IPv6
    NET: Registered PF_PACKET protocol family
    microcode: microcode updated early to new patch_level=0x0830107a
    microcode: CPU0: patch_level=0x0830107a
    microcode: CPU1: patch_level=0x0830107a
    microcode: CPU2: patch_level=0x0830107a
    ..
    microcode: CPU62: patch_level=0x0830107a
    microcode: CPU63: patch_level=0x0830107a
    microcode: Microcode Update Driver: v2.2.

which is really quite ugly and entirely pointless.

I *really* don't want to be told 129 times that my microcode has been
updated to the same level.

And yes, it's "only" 129 times, because while there are two of those
microcode update lines:

    microcode: microcode updated early to new patch_level=0x0830107a
    microcode: Microcode Update Driver: v2.2.

CPU#0 is only mentioned once, while CPU's 1..63 all get two mentions
(once for the bringup, once fro the summary).

Can we please stop doing this insanity? It's not helpful.

                 Linus

Powered by blists - more mailing lists