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: <20250414165104.2ivcicu32vfxk5qv@desk>
Date: Mon, 14 Apr 2025 09:51:04 -0700
From: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>
To: Borislav Petkov <bp@...nel.org>
Cc: Andrew Cooper <andrew.cooper3@...rix.com>,
	Josh Poimboeuf <jpoimboe@...hat.com>,
	David Kaplan <david.kaplan@....com>, X86 ML <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"Borislav Petkov (AMD)" <bp@...en8.de>
Subject: Re: [PATCH] x86/bugs: Remove X86_BUG_MMIO_UNKNOWN

On Mon, Apr 14, 2025 at 05:09:51PM +0200, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@...en8.de>
> 
> Whack this thing because:
> 
> - the "unknown" handling is done only for this vuln and not for the
>   others
> 
> - it doesn't do anything besides reporting things differently. It
>   doesn't apply any mitigations - it is simply causing unnecessary
>   complications to the code which don't bring anything besides
>   maintenance overhead to what is already a very nasty spaghetti pile
> 
> - all the currently unaffected CPUs can also be in "unknown" status so
>   there's no need for special handling here
> 
> so get rid of it.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@...en8.de>

Reviewed-by: Pawan Gupta <pawan.kumar.gupta@...ux.intel.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ