linux-kernel - Re: [PATCH v1 13/26] x86/cpuid: Scan CPUID(0x2)

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: <aBnmy_Bmf-H0wxqz@gmail.com>
Date: Tue, 6 May 2025 12:39:07 +0200
From: Ingo Molnar <mingo@...nel.org>
To: "Ahmed S. Darwish" <darwi@...utronix.de>
Cc: Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
	Dave Hansen <dave.hansen@...ux.intel.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Cooper <andrew.cooper3@...rix.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	John Ogness <john.ogness@...utronix.de>, x86@...nel.org,
	x86-cpuid@...ts.linux.dev, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v1 13/26] x86/cpuid: Scan CPUID(0x2)


* Ahmed S. Darwish <darwi@...utronix.de> wrote:

> On Tue, 06 May 2025, Ingo Molnar wrote:
> >
> > Could we please emit a one-time syslog warning & diagnostic when we run
> > across invalid or otherwise weird looking CPUID data, instead of just
> > silently skipping and sanitizing it?
> >
> 
> Sure; will do.

Thanks! We haven't been doing this for any of the current code, right? 
So depending on how frequent these messages are in practice, we might 
have to tone it down a bit - but shining a bit of light on that dark 
corner would be informative I think.

Thanks,

	Ingo