linux-kernel - Re: [PATCH v1 3/3] x86/entry: Set FRED RSP0 on return to userspace instead of context switch

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: <34964ea0-dbf5-41a1-82cb-5f677afad23c@zytor.com>
Date: Fri, 9 Aug 2024 10:37:08 -0700
From: Xin Li <xin@...or.com>
To: Nikolay Borisov <nik.borisov@...e.com>, linux-kernel@...r.kernel.org
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
        dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com,
        peterz@...radead.org, andrew.cooper3@...rix.com, seanjc@...gle.com
Subject: Re: [PATCH v1 3/3] x86/entry: Set FRED RSP0 on return to userspace
 instead of context switch

On 8/9/2024 3:45 AM, Nikolay Borisov wrote:
>> +#define TIF_LOAD_USER_STATES    30    /* Load user level states */
> 
> Wouldn't something along the l ines of TIF_LOAD_FRED_RSP be more 
> descriptive, or it's expected that this flag can cover more state in the 
> future?

Sean mentioned TIF_LOAD_FRED_RSP, however we also have FRED SSP0, which
needs to be handled similarly.

And we also want to use it to cover future states.