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>] [day] [month] [year] [list]
Message-ID: <CAKSQd8Wmkod+c6ixGa4SU9hBmwOBzL7RxwxjM6+NH6YvX3OPNQ@mail.gmail.com>
Date: Fri, 14 Nov 2025 14:13:45 -0800
From: Christian Ludloff <ludloff@...il.com>
To: Borislav Petkov <bp@...en8.de>
Cc: mario.limonciello@....com, dave.hansen@...ux.intel.com, mingo@...hat.com, 
	tglx@...utronix.de, x86@...nel.org, lkml <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86/CPU/AMD: Add additional fixed microcode for SB-7055

> @@ -224,6 +224,7 @@ static bool need_sha_check(u32 cur_rev)
>  case 0xb1010: return cur_rev <= 0xb101046; break;
>  case 0xb2040: return cur_rev <= 0xb204031; break;
>  case 0xb4040: return cur_rev <= 0xb404031; break;
> + case 0xb4041: return cur_rev <= 0xb404101; break;
>  case 0xb6000: return cur_rev <= 0xb600031; break;
>  case 0xb6080: return cur_rev <= 0xb608031; break;
>  case 0xb7000: return cur_rev <= 0xb700031; break;

Unrelated to your specific change here, but related to this list/code:

For the 0xb1010 case, microcode itself reports min_rev=0xb101040,
suggesting that its entry in this list should use <= 0xb10103f instead.

--
C.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ