[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190925141609.GC19638@linux.intel.com>
Date: Wed, 25 Sep 2019 17:16:09 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>
Cc: linux-kernel@...r.kernel.org, x86@...nel.org,
linux-sgx@...r.kernel.org, akpm@...ux-foundation.org,
dave.hansen@...el.com, sean.j.christopherson@...el.com,
nhorman@...hat.com, npmccallum@...hat.com, serge.ayoun@...el.com,
shay.katz-zamir@...el.com, haitao.huang@...el.com,
andriy.shevchenko@...ux.intel.com, tglx@...utronix.de,
kai.svahn@...el.com, josh@...htriplett.org, luto@...nel.org,
kai.huang@...el.com, rientjes@...gle.com, cedric.xing@...el.com,
Andy Lutomirski <luto@...capital.net>,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCH v22 03/24] x86/mm: x86/sgx: Signal SIGSEGV with PF_SGX
On Tue, Sep 24, 2019 at 06:04:42PM +0200, Borislav Petkov wrote:
> > + /*
> > + * Access is blocked by the Enclave Page Cache Map (EPCM), i.e. the
> > + * access is allowed by the PTE but not the EPCM. This usually happens
> > + * when the EPCM is yanked out from under us, e.g. by hardware after a
> > + * suspend/resume cycle. In any case, software, i.e. the kernel, can't
> > + * fix the source of the fault as the EPCM can't be directly modified
> > + * by software. Handle the fault as an access error in order to signal
> > + * userspace, e.g. so that userspace can rebuild their enclave(s), even
>
> s/, e.g.//
Thanks I fixed this in my tree. Also, quite many sentences seem that have
two spacebars after the end of sentence. I fixed those too.
/Jarkko
Powered by blists - more mailing lists