linux-kernel - Re: [PATCH v3 2/2] x86/sgx: Implement EUPDATESVN and opportunistically call it during first EPC page alloc

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] [day] [month] [year] [list]

Message-ID: <d16ecae1c1b4b6f06565dfe9c47849dcaeb0782c.camel@kernel.org>
Date: Fri, 02 May 2025 11:56:09 +0300
From: Jarkko Sakkinen <jarkko@...nel.org>
To: "Reshetova, Elena" <elena.reshetova@...el.com>
Cc: "Hansen, Dave" <dave.hansen@...el.com>, Sean Christopherson
 <seanjc@...gle.com>, "Huang, Kai" <kai.huang@...el.com>, 
 "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>, "Scarlata, Vincent
 R" <vincent.r.scarlata@...el.com>, "x86@...nel.org" <x86@...nel.org>, 
 "Annapurve, Vishal" <vannapurve@...gle.com>, "Cai, Chong"
 <chongc@...gle.com>, "Mallick, Asit K" <asit.k.mallick@...el.com>,  "Aktas,
 Erdem" <erdemaktas@...gle.com>, "linux-kernel@...r.kernel.org"
 <linux-kernel@...r.kernel.org>,  "bondarn@...gle.com" <bondarn@...gle.com>,
 "dionnaglaze@...gle.com" <dionnaglaze@...gle.com>,  "Raynor, Scott"
 <scott.raynor@...el.com>
Subject: Re: [PATCH v3 2/2] x86/sgx: Implement EUPDATESVN and
 opportunistically call it during first EPC page alloc

On Fri, 2025-05-02 at 07:22 +0000, Reshetova, Elena wrote:
> 
> > 
> > On Wed, Apr 30, 2025 at 06:53:32AM +0000, Reshetova, Elena wrote:
> > > 2. Switch to Sean's approach to execute EUPDATESVN during the
> > sgx_open().
> > > Btw, Sean do you agree that we don't gain much doing it second
> > > time during
> > > release() given the microcode flow?
> > > I would rather leave only one invocation of eupdatesvn during
> > sgx_inc_usage_count().
> > > 
> > > Proc: No new uABI. More predictable on svn change compared to
> > > option 1.
> > 
> > > Cons: Two explicit paths to hook: sgx_open() and sgx_vepc_open().
> > 
> > Why this is a con?
> 
> Well, just from the pov of not having a single path to enable. 
> Are you ok with option 2? 
> 

Yep, as SGX is anyway very much run-time managed feature and these
hooks fit better on how it is used.

> Best Regards,
> Elena.

BR, Jarkko