lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 22 Mar 2019 14:20:15 -0700 From: Sean Christopherson <sean.j.christopherson@...el.com> To: "Xing, Cedric" <cedric.xing@...el.com> Cc: Andy Lutomirski <luto@...nel.org>, Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>, "linux-sgx@...r.kernel.org" <linux-sgx@...r.kernel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>, "Hansen, Dave" <dave.hansen@...el.com>, "nhorman@...hat.com" <nhorman@...hat.com>, "npmccallum@...hat.com" <npmccallum@...hat.com>, "Ayoun, Serge" <serge.ayoun@...el.com>, "Katz-zamir, Shay" <shay.katz-zamir@...el.com>, "Huang, Haitao" <haitao.huang@...el.com>, "andriy.shevchenko@...ux.intel.com" <andriy.shevchenko@...ux.intel.com>, "tglx@...utronix.de" <tglx@...utronix.de>, "Svahn, Kai" <kai.svahn@...el.com>, "bp@...en8.de" <bp@...en8.de>, "josh@...htriplett.org" <josh@...htriplett.org>, "Huang, Kai" <kai.huang@...el.com>, "rientjes@...gle.com" <rientjes@...gle.com>, Dave Hansen <dave.hansen@...ux.intel.com>, Haitao Huang <haitao.huang@...ux.intel.com>, Jethro Beekman <jethro@...tanix.com>, "Dr . Greg Wettstein" <greg@...ellic.com> Subject: Re: [PATCH v19,RESEND 24/27] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions On Wed, Mar 20, 2019 at 05:17:53PM -0700, Xing, Cedric wrote: > > On Wed, Mar 20, 2019 at 12:57:52PM -0700, Xing, Cedric wrote: > > > > Using the untrusted stack as a way to exchange data is very > > > > convenient, but that doesn't mean it's a good idea. Here are some > > > > problems it > > > > causes: > > > > > > > > - It prevents using a normal function to wrap enclave entry (as > > > > we're seeing with this patch set). > > > > > > It doesn't prevent. > > > > Yes it does, keyword being "normal". Though I guess we could do a bit > > of bikeshedding on the definition of normal... > > I don't understand what you mean by "normal". My apologies, I missed the code snippet in your original code, I was thinking of a previous idea involving a JMP %rbp. Please ignore this bit of discussion.
Powered by blists - more mailing lists