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: <20251115111223.GAaRhgF1eWux9yFibX@fat_crate.local>
Date: Sat, 15 Nov 2025 12:12:23 +0100
From: Borislav Petkov <bp@...en8.de>
To: Christian Ludloff <ludloff@...il.com>
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

On Fri, Nov 14, 2025 at 02:13:45PM -0800, Christian Ludloff wrote:
> > @@ -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.

Thanks, looking at it, this is wrong too:

case 0xb0021: return cur_rev <= 0xb002146; break;

It looks like a discrepancy in the internal documentation - I'm clarifying
with microcode folks.

-- 
Regards/Gruss,
    Boris.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ