On Wed, 12 Feb 2025 at 00:31, Dave Hansen <dave.han...@intel.com> wrote: > 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.
I haven't seen a crash in either of these (always in EWB), I didn't want to imply that. But starting that sequence seems wrong knowing we cannot reclaim the page. Best regards
