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: <20241019093748.GAZxN97LS_dJ3DNrpd@fat_crate.local>
Date: Sat, 19 Oct 2024 11:37:48 +0200
From: Borislav Petkov <bp@...en8.de>
To: Jens Axboe <axboe@...nel.dk>
Cc: Thomas Gleixner <tglx@...utronix.de>,
	the arch/x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Subject: Re: AMD zen microcode updates breaks boot

On Fri, Oct 18, 2024 at 05:01:18PM -0600, Jens Axboe wrote:
> I took time out of "would otherwise have had a beer" time on a Friday

No worries, next time we meet at a conference, I'm buying! :-)

> which appears to be here:
> 
> (gdb) l *load_microcode_amd+0x334
> 0xffffffff810914a4 is in load_microcode_amd (arch/x86/kernel/cpu/microcode/amd.c:971).

Ok, first things first, this line 971 points to the code *without* my big
debugging patch. Is that correct?

With my patch that line should be 999 because of the debugging output and
other changes.

Because if so, please run with it because it has a fix for the patch matching
steppings too. And then send me the whole serial log because it'll have debug
info for me to stare at.

Thanks a lot!

-- 
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