From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,USER_AGENT_MUTT autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 245CCC04E87 for ; Thu, 16 May 2019 05:01:48 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F185120862 for ; Thu, 16 May 2019 05:01:47 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726464AbfEPFBq (ORCPT ); Thu, 16 May 2019 01:01:46 -0400 Received: from mga18.intel.com ([134.134.136.126]:50290 "EHLO mga18.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725975AbfEPFBq (ORCPT ); Thu, 16 May 2019 01:01:46 -0400 X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 May 2019 22:01:45 -0700 X-ExtLoop1: 1 Received: from jsakkine-mobl1.tm.intel.com (HELO localhost) ([10.237.50.189]) by fmsmga008.fm.intel.com with ESMTP; 15 May 2019 22:01:40 -0700 Date: Thu, 16 May 2019 08:01:50 +0300 From: Jarkko Sakkinen To: Sean Christopherson Cc: Andy Lutomirski , Jethro Beekman , "Xing, Cedric" , "Hansen, Dave" , Thomas Gleixner , "Dr. Greg" , Linus Torvalds , LKML , X86 ML , "linux-sgx@vger.kernel.org" , Andrew Morton , "nhorman@redhat.com" , "npmccallum@redhat.com" , "Ayoun, Serge" , "Katz-zamir, Shay" , "Huang, Haitao" , Andy Shevchenko , "Svahn, Kai" , Borislav Petkov , Josh Triplett , "Huang, Kai" , David Rientjes Subject: Re: [PATCH v20 00/28] Intel SGX1 support Message-ID: <20190516050150.GA6388@linux.intel.com> References: <358e9b36-230f-eb18-efdb-b472be8438b4@fortanix.com> <960B34DE67B9E140824F1DCDEC400C0F4E886094@ORSMSX116.amr.corp.intel.com> <6da269d8-7ebb-4177-b6a7-50cc5b435cf4@fortanix.com> <20190513102926.GD8743@linux.intel.com> <20190514104323.GA7591@linux.intel.com> <20190514204527.GC1977@linux.intel.com> <20190515103531.GB10917@linux.intel.com> <20190515132147.GA5875@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190515132147.GA5875@linux.intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 15, 2019 at 06:21:47AM -0700, Sean Christopherson wrote: > On Wed, May 15, 2019 at 01:35:31PM +0300, Jarkko Sakkinen wrote: > > On Tue, May 14, 2019 at 01:45:27PM -0700, Sean Christopherson wrote: > > > On Tue, May 14, 2019 at 08:13:36AM -0700, Andy Lutomirski wrote: > > > > I think it's as simple as requiring that, if SECINFO.X is set, then > > > > the src pointer points to the appropriate number of bytes of > > > > executable memory. (Unless there's some way for an enclave to change > > > > SECINFO after the fact -- is there?) > > > > > > Nit: SECINFO is just the struct passed to EADD, I think what you're really > > > asking is "can the EPCM permissions be changed after the fact". > > > > > > And the answer is, yes. > > > > > > On SGX2 hardware, the enclave can extend the EPCM permissions at runtime > > > via ENCLU[EMODPE], e.g. to make a page writable. > > > > Small correction: it is EMODPR. > > No, I'm referring to EMODPE, note the ENCLU classification. > > > Anyway, it is good to mention that these would require EACCEPT from the > > enclave side. In order to take advantage of this is in a malicous > > enclave, one would require SELinux/IMA/whatnot policy to have permitted > > it in the first place. > > EMODPE doesn't require EACCEPT or any equivalent from the kernel. As > you alluded to, the page tables would still need to allow PROT_EXEC. I > was simply trying to answer Andy's question regarding SECINFO. Ah, have to admit that I had totally forgot EMODPE :-) Have not had to deal with that opcode that much. /Jarkko