Don Porter
Don Porter
Sorry to be late to the party; if this is still under active discussion, my main question is whether we could build this and exitless support on the same substrate?
3. Consistent naming in the SGX PAL for code that runs in and out of the enclave 4. PAL/common/unix for common code to any unix host.
Agreed. I think shim_file_data is probably the one we want.
Thanks for the report! Do you happen to have a simple test case (or know of an LTP test) that illustrates the issue succinctly?
Large directories may not be able to read in one pass, so offset is important. That said, we should have well-defined units for what offset is in terms of.
I don't agree with this: I would prefer to have minimally stateful PAL abstractions, including handles without implicit cursors. Otherwise, this can create problems for checkpoint/migrate/restore. But I also don't...
Thanks for the suggestion. In future work, we'd like to do a secure version of this, but it is non-trivial. An insecure version is relatively easy, but I hesitate to...
Hi! I'd like to help. Can you share the dockerfile/code you are trying to build, and the commands to reproduce this issue? Thanks!