From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jethro Beekman <jethro@fortanix.com>
Cc: "linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>
Subject: Re: Unable to load large enclave
Date: Wed, 30 Sep 2020 14:45:54 +0300 [thread overview]
Message-ID: <20200930114554.GA7612@linux.intel.com> (raw)
In-Reply-To: <81e38a1b-c9a7-209e-76f5-e2c91f49c1e3@fortanix.com>
On Wed, Sep 30, 2020 at 09:12:06AM +0200, Jethro Beekman wrote:
> On 2020-09-30 03:16, Jarkko Sakkinen wrote:
> > On Tue, Sep 29, 2020 at 05:52:48PM +0200, Jethro Beekman wrote:
> >> Since the latest API changes, I'm unable to load a large enclave. The
> >> test program at
> >> https://github.com/fortanix/rust-sgx/blob/sgx-load-large-enclave-test/src/main.rs
> >> always fails with ENOMEM after loading 0xffd6 pages.
> >>
> >> I've tested this with v36, if there's reason to believe it has been
> >> fixed I'd be happy to try it out on a newer patch set.
> >
> > I recommend using v39-rc1 tag that I created for testing because API is
> > reverted back to be compatible with v36.
>
> Not sure what you're saying. I tested with v36. You're saying v39-rc1
> will be the same? Or did you fix the issue since v36?
v37 and v38 has an API change that is reverted in v39:
https://lore.kernel.org/linux-sgx/20200921195822.GA58176@linux.intel.com/
I'm not sure of the root cause yet but you asked to try to out a newer
patch set and v39-rc1 is the best option.
There was off-by-one error in enclave maximum size calculation fixed in
v37 (it was actually a bug in SDM inherited to the code) but that should
not result the situation you just described.
/Jarkko
next prev parent reply other threads:[~2020-09-30 11:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 15:52 Unable to load large enclave Jethro Beekman
2020-09-30 1:16 ` Jarkko Sakkinen
2020-09-30 7:12 ` Jethro Beekman
2020-09-30 11:45 ` Jarkko Sakkinen [this message]
2020-10-03 13:12 ` Jarkko Sakkinen
2020-10-05 22:56 ` Sean Christopherson
2020-10-06 15:13 ` Jarkko Sakkinen
2020-10-07 15:49 ` Jarkko Sakkinen
2020-10-07 16:13 ` Jethro Beekman
2020-10-07 17:20 ` Jarkko Sakkinen
2020-10-07 18:14 ` Jethro Beekman
2020-10-07 18:34 ` Jarkko Sakkinen
2020-10-07 18:36 ` Jarkko Sakkinen
2020-10-07 18:25 ` Jarkko Sakkinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200930114554.GA7612@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.