linux-kernel - Re: [PATCH] x86: sgx: Don't track poisoned pages for reclaiming

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: <7ed9b288-69a2-446c-9f7f-50ef6bc56673@intel.com>
Date: Tue, 11 Feb 2025 15:31:54 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: "Huang, Kai" <kai.huang@...el.com>, Jarkko Sakkinen <jarkko@...nel.org>
Cc: Andrew Zaborowski <andrew.zaborowski@...el.com>, x86@...nel.org,
 linux-sgx@...r.kernel.org, linux-kernel@...r.kernel.org,
 Dave Hansen <dave.hansen@...ux.intel.com>, Tony Luck <tony.luck@...el.com>,
 Thomas Gleixner <tglx@...utronix.de>, Borislav Petkov <bp@...en8.de>,
 Ingo Molnar <mingo@...hat.com>, "H . Peter Anvin" <hpa@...or.com>,
 balrogg@...il.com
Subject: Re: [PATCH] x86: sgx: Don't track poisoned pages for reclaiming

On 2/11/25 13:18, Huang, Kai wrote:
>>> This requires low-level SGX implementation knowledge to fully
>>> understand. Both what "ETRACK, EBLOCK and EWB" are in the first place,
>>> how they are involved in reclaim and also why EREMOVE doesn't lead to
>>> the same fate.
>>
>> Does it? [I'll dig up Intel SDM to check this]
>>
> I just did. 🙂
> 
> It seems EREMOVE only reads and updates the EPCM entry for the target
> EPC page but won't actually access that EPC page.

Actually, now that I think about it even more, why would ETRACK or
EBLOCK access the page itself? They seem superficially like they'd be
metadata-only too.