linux-kernel - Re: [PATCH] x86/microcode: Fix crashes on early 486 CPUs due to usage of 'cpuid'.

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20250408092016.27c8ec942a82459e1a9b9997@ombertech.com>
Date: Tue, 8 Apr 2025 09:20:16 +1000
From: Kevin Koster <lkml@...ertech.com>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Borislav Petkov <bp@...en8.de>, Thomas Gleixner <tglx@...utronix.de>,
 Oerg866 <oerg866@...glemail.com>, linux-kernel@...r.kernel.org, Ingo Molnar
 <mingo@...hat.com>, Dave Hansen <dave.hansen@...ux.intel.com>,
 x86@...nel.org
Subject: Re: [PATCH] x86/microcode: Fix crashes on early 486 CPUs due to
 usage of 'cpuid'.

On Mon, 07 Apr 2025 07:38:59 -0700
"H. Peter Anvin" <hpa@...or.com> wrote:
> Can you please not post stack traces without any symbol information
> either internal or external? It is just random hex digits in the
> absence of a System.map or vmlinux file.

OK, I'll replace them with "[snip stack trace]" in future unless asked
for the System.map file too.