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  linux-cve-announce  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]
Message-ID: <b167addc-aa6b-d844-6d77-9efbd229b16d@intel.com>
Date:   Mon, 19 Jul 2021 11:28:09 -0700
From:   Dave Hansen <dave.hansen@...el.com>
To:     Tony Luck <tony.luck@...el.com>,
        Sean Christopherson <seanjc@...gle.com>,
        Jarkko Sakkinen <jarkko.sakkinen@...el.com>
Cc:     x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 1/6] x86/sgx: Provide indication of life-cycle of EPC
 pages

On 7/19/21 11:20 AM, Tony Luck wrote:
> 1) Change the type of "owner" to "void *" (it can have other types
>    besides "struct sgx_encl_page *).

I see:

static int __sgx_vepc_fault(struct sgx_vepc *vepc,
{
...
        epc_page = sgx_alloc_epc_page(vepc, false);

where sgx_alloc_epc_page() sets page->owner=vepc.  But, I don't see a
*reader* anywhere.  Do we actually use that vepc anywhere?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ