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
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 10 Aug 2020 17:52:09 -0700
From:   Andy Lutomirski <>
To:     Sean Christopherson <>
Cc:     Andy Lutomirski <>,
        Nathaniel McCallum <>,
        Jarkko Sakkinen <>,
        X86 ML <>,,
        LKML <>,
        Jethro Beekman <>,
        Cedric Xing <>,
        Andrew Morton <>,
        Andy Shevchenko <>,, Borislav Petkov <>,, Conrad Parker <>,, Dave Hansen <>,
        "Huang, Haitao" <>,
        Josh Triplett <>,
        "Huang, Kai" <>,
        "Svahn, Kai" <>, Keith Moyer <>,
        Christian Ludloff <>,
        Neil Horman <>,
        Patrick Uiterwijk <>,
        David Rientjes <>,
        Thomas Gleixner <>,
Subject: Re: [PATCH v36 21/24] x86/vdso: Implement a vDSO for Intel SGX enclave call

> On Aug 10, 2020, at 4:48 PM, Sean Christopherson <> wrote:
> ´╗┐On Mon, Aug 10, 2020 at 04:08:46PM -0700, Andy Lutomirski wrote:
>> What am I missing?  I still don't really understand why we are
>> supporting this mechanism at all.  Just the asm code to invoke the
>> callback seems to be about half of the entire function.
> Because the Intel SDK (and other SDKs?) wants to use the host stack to pass
> parameters out of the enclave.

Ugh, right.  I forgot about that particular abomination.

I suppose that passing a context pointer would be reasonable.

Powered by blists - more mailing lists