| 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
| ||
|
Date: Tue, 21 Sep 2021 13:23:58 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Tony Luck <tony.luck@...el.com>,
Sean Christopherson <seanjc@...gle.com>,
Jarkko Sakkinen <jarkko@...nel.org>
Cc: Cathy Zhang <cathy.zhang@...el.com>, linux-sgx@...r.kernel.org,
x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 2/7] x86/sgx: Add infrastructure to identify SGX EPC
pages
On 9/17/21 2:38 PM, Tony Luck wrote:
> /*
> * These variables are part of the state of the reclaimer, and must be accessed
> @@ -649,6 +650,9 @@ static bool __init sgx_setup_epc_section(u64 phys_addr, u64 size,
> }
>
> section->phys_addr = phys_addr;
> + section->end_phys_addr = phys_addr + size - 1;
> + xa_store_range(&epc_page_ranges, section->phys_addr,
> + section->end_phys_addr, section, GFP_KERNEL);
Did we ever figure out how much space storing really big ranges in the
xarray consumes?
Powered by blists - more mailing lists