Dmitrii Kuvaiskii
Dmitrii Kuvaiskii
@oshogbo completed all the required tasks, closing this meta-issue.
Jenkins, test this please
Jenkins, test this please
Hello, a Gramine maintainer here. I accidentally stumbled upon this PR. > It forces you to switch to ring 3, a very inelegant and costly design quirk. Compared to other...
@jonathan-sha Thanks for a great description of the problem! This was already discussed in #1134, so I'm not sure if we should consider this issue a duplicate and move your...
@vijaydhanraj You're working on this, right? Let me assign you now, and if this is wrong, please reply and I'll remove the assignment. UPDATE: I forgot that I can't assign...
@kailun-qin The proposed changes and flow look correct to me. Below are some notes. 1. I see no reason to exclude the Linux PAL from handling `MAP_NORESERVE`. I think you...
> > And only in cases where this path will be triggered, we can immediately check whether the faulting address is zero, and if it is then we loudly fail...
> > If our current LibOS #PF handler doesn't check sgx.require_exinfo and propagates the address to the app anyway, then we have a bug. > > Ah OK, I don't...
I have two new notes: ### All #PF handling must be inside the SGX PAL > On page fault handling, specifically in `memfault_upcall()` ... The original design by Kailun uses...