public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Reshetova, Elena" <elena.reshetova@intel.com>
Cc: "Hansen, Dave" <dave.hansen@intel.com>,
	"jarkko@kernel.org" <jarkko@kernel.org>,
	"seanjc@google.com" <seanjc@google.com>,
	"Huang, Kai" <kai.huang@intel.com>,
	"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>,
	"Mallick, Asit K" <asit.k.mallick@intel.com>,
	"Scarlata, Vincent R" <vincent.r.scarlata@intel.com>,
	"Cai, Chong" <chongc@google.com>,
	"Aktas, Erdem" <erdemaktas@google.com>,
	"Annapurve, Vishal" <vannapurve@google.com>,
	"dionnaglaze@google.com" <dionnaglaze@google.com>,
	"bondarn@google.com" <bondarn@google.com>,
	"Raynor, Scott" <scott.raynor@intel.com>
Subject: Re: [PATCH v5 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves
Date: Mon, 19 May 2025 14:51:39 +0200	[thread overview]
Message-ID: <aCspW0MweLoODLC8@gmail.com> (raw)
In-Reply-To: <DM8PR11MB57504A6B41329214262E16E2E79CA@DM8PR11MB5750.namprd11.prod.outlook.com>


* Reshetova, Elena <elena.reshetova@intel.com> wrote:

>  
> > * Elena Reshetova <elena.reshetova@intel.com> wrote:
> > 
> > > @@ -19,10 +19,15 @@ static int sgx_open(struct inode *inode, struct file
> > *file)
> > >  	struct sgx_encl *encl;
> > >  	int ret;
> > >
> > > +	ret = sgx_inc_usage_count();
> > > +	if (ret)
> > > +		return -EBUSY;
> > 
> > So if sgx_inc_usage_count() returns nonzero, it's in use already and we
> > return -EBUSY, right?
> 
> I guess my selection of error code here was wrong. 
> The intended logic is if sgx_inc_usage_count() returns nonzero,
> the *incrementing of counter failed* (due to failed EUPDATESVN)
> and we want to stop and report error.
>   
> > 
> > But:
> > 
> > >  int sgx_inc_usage_count(void)
> > >  {
> > > +	int ret;
> > > +
> > > +	/*
> > > +	 * Increments from non-zero indicate EPC other
> > > +	 * active EPC users and EUPDATESVN is not attempted.
> > > +	 */
> > > +	if (atomic64_inc_not_zero(&sgx_usage_count))
> > > +		return 0;
> > 
> > If sgx_usage_count is 1 here (ie. it's busy), this will return *zero*,
> > and sgx_open() will not run into the -EBUSY condition and will continue
> > assuming it has claimed the usage count, while it hasn't ...
> 
> Yes, meaning is different, see above. 

So that's rather convoluted:

	atomic64_inc_not_zero():   returns 1 on successful increase, 0 on failure
        sgx_inc_usage_count():     returns 0 on successful increase, 1 on failure
        sgx_open():                returns 0 on successful increase, -EBUSY on failure

Could we at least standardize sgx_inc_usage_count() on -EBUSY in the 
failure case, so it's a more obvious pattern:

+       ret = sgx_inc_usage_count();
+       if (ret < 0)
+               return ret;

Thanks,

	Ingo

  reply	other threads:[~2025-05-19 12:51 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-19  7:24 [PATCH v5 0/5] Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-05-19  7:24 ` [PATCH v5 1/5] x86/sgx: Introduce a counter to count the sgx_(vepc_)open() Elena Reshetova
2025-05-19 10:47   ` Huang, Kai
2025-05-19 11:35     ` Huang, Kai
2025-05-19 11:43       ` Reshetova, Elena
2025-05-19 11:47     ` Reshetova, Elena
2025-05-19 17:28       ` Jarkko Sakkinen
2025-05-19 22:34       ` Huang, Kai
2025-05-20  6:22         ` Reshetova, Elena
2025-05-19 17:21   ` Jarkko Sakkinen
2025-05-20  6:25     ` Reshetova, Elena
2025-05-20 19:55       ` Jarkko Sakkinen
2025-05-19  7:24 ` [PATCH v5 2/5] x86/cpufeatures: Add X86_FEATURE_SGX_EUPDATESVN feature flag Elena Reshetova
2025-05-19  7:47   ` Ingo Molnar
2025-05-19 11:29     ` Reshetova, Elena
2025-05-19 10:53   ` Huang, Kai
2025-05-19 11:29     ` Reshetova, Elena
2025-05-19  7:24 ` [PATCH v5 3/5] x86/sgx: Define error codes for use by ENCLS[EUPDATESVN] Elena Reshetova
2025-05-19 10:57   ` Huang, Kai
2025-05-19 11:30     ` Reshetova, Elena
2025-05-19 11:36       ` Huang, Kai
2025-05-19  7:24 ` [PATCH v5 4/5] x86/sgx: Implement ENCLS[EUPDATESVN] Elena Reshetova
2025-05-19 11:32   ` Huang, Kai
2025-05-19 11:41     ` Reshetova, Elena
2025-05-19 22:45       ` Huang, Kai
2025-05-20  6:36         ` Reshetova, Elena
2025-05-20 10:42           ` Huang, Kai
2025-05-19 16:02   ` Dave Hansen
2025-05-19 18:24   ` Jarkko Sakkinen
2025-05-20  6:31     ` Reshetova, Elena
2025-05-20 19:57       ` Jarkko Sakkinen
2025-05-20 20:00         ` Dave Hansen
2025-05-19  7:24 ` [PATCH v5 5/5] x86/sgx: Enable automatic SVN updates for SGX enclaves Elena Reshetova
2025-05-19  8:00   ` Ingo Molnar
2025-05-19 11:27     ` Reshetova, Elena
2025-05-19 12:51       ` Ingo Molnar [this message]
2025-05-20  6:43         ` Reshetova, Elena
2025-05-20  7:22           ` Ingo Molnar
2025-05-19 18:32   ` Jarkko Sakkinen
2025-05-20  6:46     ` 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=aCspW0MweLoODLC8@gmail.com \
    --to=mingo@kernel.org \
    --cc=asit.k.mallick@intel.com \
    --cc=bondarn@google.com \
    --cc=chongc@google.com \
    --cc=dave.hansen@intel.com \
    --cc=dionnaglaze@google.com \
    --cc=elena.reshetova@intel.com \
    --cc=erdemaktas@google.com \
    --cc=jarkko@kernel.org \
    --cc=kai.huang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sgx@vger.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