From: "Huang, Kai" <kai.huang@intel.com>
To: "Reshetova, Elena" <elena.reshetova@intel.com>,
"Hansen, Dave" <dave.hansen@intel.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
"x86@kernel.org" <x86@kernel.org>,
"jarkko@kernel.org" <jarkko@kernel.org>,
"Annapurve, Vishal" <vannapurve@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mallick, Asit K" <asit.k.mallick@intel.com>,
"Aktas, Erdem" <erdemaktas@google.com>,
"Cai, Chong" <chongc@google.com>,
"Bondarevska, Nataliia" <bondarn@google.com>,
"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v12 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves
Date: Mon, 11 Aug 2025 10:50:29 +0000 [thread overview]
Message-ID: <74fd32cecdd42cb45d88a96a1dbb6d74cb39594d.camel@intel.com> (raw)
In-Reply-To: <20250811090751.683841-6-elena.reshetova@intel.com>
>
> +/* Mutex to ensure no concurrent EPC accesses during EUPDATESVN */
> +static DEFINE_MUTEX(sgx_svn_lock);
> +
> int sgx_inc_usage_count(void)
> {
> + guard(mutex)(&sgx_svn_lock);
> +
> + if (sgx_usage_count++ == 0)
> + return sgx_update_svn();
> +
Hmm.. sorry for not noticing this before.. But I think we might have a
problem here since the sgx_usage_count is increased regardless of the
result of sgx_update_svn().
If sgx_update_svn() fails, it makes sgx_inc_usage_count() return error
too, so sgx_{vepc_}open() will fail and return immediately w/o calling
sgx_dec_usage_count().
But the sgx_usage_count has been increased.
AFAICT when sgx_{vepc_}_open() fails, the sgx_{vepc_}release() is not
called, so sgx_dec_usage_count() is never called and sgx_usage_count
remains increased.
So when sgx_{vepc_}open() calls sgx_inc_usage_count() again, it will skip
calling sgx_update_svn(), and allow enclave/vEPC to be created
successfully, which just defeats the purpose.
So if I am not missing anything, I think we should only increase the count
when sgx_update_svn() returns success?
> return 0;
> }
>
> void sgx_dec_usage_count(void)
> {
> - return;
> + sgx_usage_count--;
> }
>
> static int __init sgx_init(void)
next prev parent reply other threads:[~2025-08-11 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 9:06 [PATCH v12 0/5] " Elena Reshetova
2025-08-11 9:06 ` [PATCH v12 1/5] x86/sgx: Introduce functions to count the sgx_(vepc_)open() Elena Reshetova
2025-08-11 10:23 ` Huang, Kai
2025-08-11 9:06 ` [PATCH v12 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-08-11 9:06 ` [PATCH v12 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-08-11 10:23 ` Huang, Kai
2025-08-11 9:06 ` [PATCH v12 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-08-11 9:06 ` [PATCH v12 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-08-11 10:50 ` Huang, Kai [this message]
2025-08-11 12:14 ` Reshetova, Elena
2025-08-11 20:37 ` Huang, Kai
2025-08-12 4:56 ` Reshetova, Elena
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74fd32cecdd42cb45d88a96a1dbb6d74cb39594d.camel@intel.com \
--to=kai.huang@intel.com \
--cc=asit.k.mallick@intel.com \
--cc=bondarn@google.com \
--cc=chongc@google.com \
--cc=dave.hansen@intel.com \
--cc=elena.reshetova@intel.com \
--cc=erdemaktas@google.com \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=scott.raynor@intel.com \
--cc=seanjc@google.com \
--cc=vannapurve@google.com \
--cc=vincent.r.scarlata@intel.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®