linux-kernel - Re: [PATCH v1 1/1] x86/fred: Fix int80 emulation for FRED

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]

Date: Tue, 16 Apr 2024 11:11:44 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Borislav Petkov <bp@...en8.de>
Cc: "Xin Li (Intel)" <xin@...or.com>, linux-kernel@...r.kernel.org,
        luto@...nel.org, tglx@...utronix.de, mingo@...hat.com,
        dave.hansen@...ux.intel.com, x86@...nel.org
Subject: Re: [PATCH v1 1/1] x86/fred: Fix int80 emulation for FRED

On 4/16/24 11:07, Borislav Petkov wrote:
> On Tue, Apr 16, 2024 at 11:05:09AM -0700, H. Peter Anvin wrote:
>> The question was if you wanted a quick fix for x86/urgent. It's pretty
>> obvious that a FRED fork of the int80 code is called for.
> 
> Yeah, I'm thinking the FRED fork would be even easier to send to Linus
> now since no existing hw will break.

Looking at the resulting code (Xin's v2 path), I would agree with you. 
The code is downright trivial.

> Btw, I presume that patch needs to have
> 
> Fixes: 55617fb991df ("x86/entry: Do not allow external 0x80 interrupts")
> 

Yes. My fault, I gave Xin incorrect information w.r.t. Fixes: tags.

	-hpa