From: Dave Hansen <dave.hansen@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
sean.j.christopherson@intel.com, jarkko@kernel.org, bp@suse.de,
x86@kernel.org
Subject: [PATCH] x86/sgx: rename and document SGX bit lock
Date: Tue, 12 Jan 2021 14:19:01 -0800 [thread overview]
Message-ID: <20210112221901.2CE31C8E@viggo.jf.intel.com> (raw)
SGX ioctl() calls are serialized with a lock. It's a weird open-coded
lock that is not even called a "lock". That makes it a weird beast,
but Sean has convinced me it's a good idea without better alternatives.
Give the lock bit a better name, and document what it actually trying
to do.
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Jarkko Sakkinen <jarkko@kernel.org>
Cc: Borislav Petkov <bp@suse.de>
Cc: x86@kernel.org
---
b/arch/x86/kernel/cpu/sgx/encl.h | 2 +-
b/arch/x86/kernel/cpu/sgx/ioctl.c | 19 ++++++++++++++++---
2 files changed, 17 insertions(+), 4 deletions(-)
diff -puN arch/x86/kernel/cpu/sgx/ioctl.c~sgx-encl-flags arch/x86/kernel/cpu/sgx/ioctl.c
--- a/arch/x86/kernel/cpu/sgx/ioctl.c~sgx-encl-flags 2021-01-12 14:02:24.480689006 -0800
+++ b/arch/x86/kernel/cpu/sgx/ioctl.c 2021-01-12 14:02:24.486689006 -0800
@@ -690,8 +690,21 @@ long sgx_ioctl(struct file *filep, unsig
struct sgx_encl *encl = filep->private_data;
int ret;
- if (test_and_set_bit(SGX_ENCL_IOCTL, &encl->flags))
- return -EBUSY;
+ /*
+ * Behold, the Big SGX Lock
+ *
+ * The primary function of this "lock" is to actively discourage
+ * attempts at multi-threaded enclave management. Enclave management
+ * is fundamentally a single-threaded affair. Enclave measurement,
+ * for instance would be worthless if two ADD_PAGES instances raced
+ * and occurred in different orders.
+ *
+ * encl->lock is ill suited for this because it would need to be
+ * conditionally dropped and reqacuired for operations like enclave
+ * page allocation and reclaim.
+ */
+ if (test_and_set_bit(SGX_ENCL_IOCTL_LOCK, &encl->flags))
+ return -EINVAL;
switch (cmd) {
case SGX_IOC_ENCLAVE_CREATE:
@@ -711,6 +724,6 @@ long sgx_ioctl(struct file *filep, unsig
break;
}
- clear_bit(SGX_ENCL_IOCTL, &encl->flags);
+ clear_bit(SGX_ENCL_IOCTL_LOCK, &encl->flags);
return ret;
}
diff -puN arch/x86/kernel/cpu/sgx/encl.h~sgx-encl-flags arch/x86/kernel/cpu/sgx/encl.h
--- a/arch/x86/kernel/cpu/sgx/encl.h~sgx-encl-flags 2021-01-12 14:02:24.482689006 -0800
+++ b/arch/x86/kernel/cpu/sgx/encl.h 2021-01-12 14:16:37.511686879 -0800
@@ -34,7 +34,7 @@ struct sgx_encl_page {
};
enum sgx_encl_flags {
- SGX_ENCL_IOCTL = BIT(0),
+ SGX_ENCL_IOCTL_LOCK = BIT(0), /* See sgx_ioctl() */
SGX_ENCL_DEBUG = BIT(1),
SGX_ENCL_CREATED = BIT(2),
SGX_ENCL_INITIALIZED = BIT(3),
_
next reply other threads:[~2021-01-12 22:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 22:19 Dave Hansen [this message]
2021-01-13 22:04 ` [PATCH] x86/sgx: rename and document SGX bit lock 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=20210112221901.2CE31C8E@viggo.jf.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@suse.de \
--cc=jarkko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sean.j.christopherson@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