Re: [PATCH v26 10/22] x86/sgx: Linux Enclave Driver

From
Sean Christopherson <hidden>
Date
2020-02-14 17:11:52
Also in
lkml
Reply to
Jethro Beekman, 2020-02-14
On Fri, Feb 14, 2020 at 10:24:10AM +0100, Jethro Beekman wrote:
On 2020-02-13 19:07, Sean Christopherson wrote:
quoted
On Thu, Feb 13, 2020 at 02:59:52PM +0100, Jethro Beekman wrote:
quoted
On 2020-02-09 22:25, Jarkko Sakkinen wrote:
quoted
+/**
+ * struct sgx_enclave_add_pages - parameter structure for the
+ *                                %SGX_IOC_ENCLAVE_ADD_PAGE ioctl
+ * @src:	start address for the page data
+ * @offset:	starting page offset
+ * @length:	length of the data (multiple of the page size)
+ * @secinfo:	address for the SECINFO data
+ * @flags:	page control flags
+ * @count:	number of bytes added (multiple of the page size)
+ */
+struct sgx_enclave_add_pages {
+	__u64	src;
+	__u64	offset;
+	__u64	length;
+	__u64	secinfo;
+	__u64	flags;
+	__u64	count;
+};
Compared to the last time I looked at the patch set, this API removes the
ability to measure individual pages chunks. That is not acceptable.
Why is it not acceptable?  E.g. what specific use case do you have that
_requires_ on measuring partial 4k pages of an enclave?
The use case is someone gives me an enclave and I want to load it. If I don't
load it exactly as the enclave author specified, the enclave hash will be
different, and it won't work.
And if our ABI says "thou shall measure in 4k chunks", then it's an invalid
enclave if its author generated MRENCLAVE using a different granularity.
Thread (24 messages) 24 messages, 7 authors, last reply 2020-02-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help