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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4b4ecaa1-2ace-43bf-b71b-0de78bcf113c@intel.com>
Date: Fri, 25 Apr 2025 15:07:00 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Elena Reshetova <elena.reshetova@...el.com>,
 "jarkko@...nel.org" <jarkko@...nel.org>, Kai Huang <kai.huang@...el.com>,
 "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>,
 Vincent Scarlata <vincent.r.scarlata@...el.com>,
 "x86@...nel.org" <x86@...nel.org>, Vishal Annapurve <vannapurve@...gle.com>,
 Chong Cai <chongc@...gle.com>, Asit K Mallick <asit.k.mallick@...el.com>,
 Erdem Aktas <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>,
 Scott Raynor <scott.raynor@...el.com>
Subject: Re: [PATCH v3 2/2] x86/sgx: Implement EUPDATESVN and
 opportunistically call it during first EPC page alloc

On 4/25/25 14:58, Sean Christopherson wrote:
> On Fri, Apr 25, 2025, Dave Hansen wrote:
>> On 4/25/25 14:04, Sean Christopherson wrote:
>>> Userspace is going to be waiting on ->release() no matter what.
>> Unless it isn't even involved and it happens automatically.
> With my Google hat on: no thanks.

I'm completely open to the idea of adding transparency so that folks can
tell when the SVN increments. I'm mostly open to having a new ABI to do
it explicitly in addition to doing it implicitly.]

> Coupled with adding latency to launching the 0=>1 enclave, just to
> handle something that happens a few times per year, and I don't see
> any value in automatic updates. Maybe it sounds nice on paper, but
> from my perspective, I see nothing but pain.
I'm not worried about the latency until I see numbers. If the number
show it's horrible, then we either change course or go yell at the folks
who wrote the xucode.