From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-sgx@vger.kernel.org
Cc: sean.j.christopherson@intel.com, shay.katz-zamir@intel.com,
serge.ayoun@intel.com
Subject: x86/sgx: v23-rc1
Date: Wed, 9 Oct 2019 17:07:23 +0300 [thread overview]
Message-ID: <20191009140723.GA18318@linux.intel.com> (raw)
Baseline before adding Sean's updates. This contains only my updates. I
spent this day mostly fixing diff's. Especially these two were somewhat
unclean:
1. x86/sgx: Add a page reclaimer
2. x86/sgx: Linux Enclave Driver
Now they pile up nicely (I think). So I decided to do this tag since now
commit's in the sense of form and shape are legit. And also because
things, well, work.
I'll continue from this by integrating Sean's changes. You can see below
what has been already changed.
/Jarkko
tag v23-rc1
Tagger: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Date: Wed Oct 9 16:59:10 2019 +0300
x86/sgx: v23-rc1 patch set
* Return -EIO instead of -ECANCELED when ptrace() fails to read a TCS page.
* In the reclaimer, pin page before ENCLS[EBLOCK] because pinning can fail
(because of OOM) even in legit behaviour and after EBLOCK the reclaiming
flow can be only reverted by killing the whole enclave.
* Fixed SGX_ATTR_RESERVED_MASK. Bit 7 was marked as reserved while in fact
it should have been bit 6 (Table 37-3 in the SDM).
* Return -EPERM from SGX_IOC_ENCLAVE_INIT when ENCLS[EINIT] returns an SGX
error code.
-----BEGIN PGP SIGNATURE-----
iJYEABYIAD4WIQRE6pSOnaBC00OEHEIaerohdGur0gUCXZ3nxCAcamFya2tvLnNh
a2tpbmVuQGxpbnV4LmludGVsLmNvbQAKCRAaerohdGur0mKVAQDcmIGs2f8y8hDY
b7zaQdNbaAMgsEkQ3ohMA88fbm2UQwD+P7y5AcAxzdccbgh++7RDy6XR2Ow2pluW
vCGUvRAhgwY=
=LCI3
-----END PGP SIGNATURE-----
/Jarkko
next reply other threads:[~2019-10-09 14:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 14:07 Jarkko Sakkinen [this message]
2019-10-09 14:35 ` x86/sgx: v23-rc1 Jarkko Sakkinen
2019-10-10 7:34 ` Jarkko Sakkinen
2019-10-10 7:38 ` Jarkko Sakkinen
2019-10-10 8:07 ` Jarkko Sakkinen
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=20191009140723.GA18318@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=serge.ayoun@intel.com \
--cc=shay.katz-zamir@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).