From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: linux-sgx@vger.kernel.org
Cc: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
Haitao Huang <haitao.huang@linux.intel.com>,
Matthew Wilcox <willy@infradead.org>,
Sean Christopherson <sean.j.christopherson@intel.com>,
Jethro Beekman <jethro@fortanix.com>,
Dave Hansen <dave.hansen@linux.intel.com>
Subject: [PATCH v3] x86/sgx: Fix sgx_encl_may_map locking
Date: Mon, 5 Oct 2020 17:11:19 +0300 [thread overview]
Message-ID: <20201005141119.5395-1-jarkko.sakkinen@linux.intel.com> (raw)
Fix the issue further discussed in:
1. https://lore.kernel.org/linux-sgx/op.0rwbv916wjvjmi@mqcpg7oapc828.gar.corp.intel.com/
2. https://lore.kernel.org/linux-sgx/20201003195440.GD20115@casper.infradead.org/
Reported-by: Haitao Huang <haitao.huang@linux.intel.com>
Suggested-by: Matthew Wilcox <willy@infradead.org>
Cc: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: Jethro Beekman <jethro@fortanix.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
---
v3:
* Added the missing unlock pointed out by Matthew.
* Tested with the correct patch (last time had v1 applied)
* I don't know what happened to v2 changelog, checked from patchwork
and it wasn't there. Hope this is not scraped.
arch/x86/kernel/cpu/sgx/encl.c | 29 +++++++++++++++++++++++++----
1 file changed, 25 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/cpu/sgx/encl.c b/arch/x86/kernel/cpu/sgx/encl.c
index 4c6407cd857a..e91e521b03a8 100644
--- a/arch/x86/kernel/cpu/sgx/encl.c
+++ b/arch/x86/kernel/cpu/sgx/encl.c
@@ -307,6 +307,8 @@ int sgx_encl_may_map(struct sgx_encl *encl, unsigned long start,
unsigned long idx_start = PFN_DOWN(start);
unsigned long idx_end = PFN_DOWN(end - 1);
struct sgx_encl_page *page;
+ unsigned long count = 0;
+ int ret = 0;
XA_STATE(xas, &encl->page_array, idx_start);
@@ -317,11 +319,30 @@ int sgx_encl_may_map(struct sgx_encl *encl, unsigned long start,
if (current->personality & READ_IMPLIES_EXEC)
return -EACCES;
- xas_for_each(&xas, page, idx_end)
- if (!page || (~page->vm_max_prot_bits & vm_prot_bits))
- return -EACCES;
+ /*
+ * No need to hold encl->lock:
+ * 1. None of the page->* get written.
+ * 2. page->vm_max_prot_bits is set in sgx_encl_page_alloc(). This
+ * is before calling xa_insert(). After that it is never modified.
+ */
+ xas_lock(&xas);
+ xas_for_each(&xas, page, idx_end) {
+ if (++count % XA_CHECK_SCHED)
+ continue;
- return 0;
+ if (!page || (~page->vm_max_prot_bits & vm_prot_bits)) {
+ ret = -EACCES;
+ break;
+ }
+
+ xas_pause(&xas);
+ xas_unlock(&xas);
+ cond_resched();
+ xas_lock(&xas);
+ }
+ xas_unlock(&xas);
+
+ return ret;
}
static int sgx_vma_mprotect(struct vm_area_struct *vma,
--
2.25.1
next reply other threads:[~2020-10-05 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 14:11 Jarkko Sakkinen [this message]
2020-10-05 14:12 ` [PATCH v3] x86/sgx: Fix sgx_encl_may_map locking Matthew Wilcox
2020-10-05 17:25 ` Jarkko Sakkinen
2020-10-05 17:28 ` Jarkko Sakkinen
2020-10-05 14:28 ` Dave Hansen
2020-10-05 17:36 ` Jarkko Sakkinen
2020-10-05 15:55 ` Sean Christopherson
2020-10-05 17:41 ` Jarkko Sakkinen
2020-10-05 17:43 ` 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=20201005141119.5395-1-jarkko.sakkinen@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=haitao.huang@linux.intel.com \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@intel.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).