Intel SGX development
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko.sakkinen@iki.fi>
To: Dave Hansen <dave.hansen@intel.com>
Cc: "Sakkinen, Jarkko" <jarkko.sakkinen@intel.com>,
	"Luck, Tony" <tony.luck@intel.com>,
	"linux-sgx@vger.kernel.org" <linux-sgx@vger.kernel.org>,
	"Accardi, Kristen C" <kristen.c.accardi@intel.com>,
	"Chatre, Reinette" <reinette.chatre@intel.com>
Subject: Re: Testing 5.17 bugfix material
Date: Sun, 23 Jan 2022 01:41:39 +0200	[thread overview]
Message-ID: <YeyWMxWzvpEywbUx@iki.fi> (raw)
In-Reply-To: <53bf06e8-f523-83db-ed4d-039c34f634cd@intel.com>

On Fri, Jan 21, 2022 at 11:57:50AM -0800, Dave Hansen wrote:
> Hi Everyone,
> 
> There are a few SGX fixes that have showed up in the last week or so,
> mostly around RAS and fixing the backing storage issues.  Could folks
                ~~~

Remote ATtestation?

> please give this branch a good thrashing?
> 
> > https://git.kernel.org/pub/scm/linux/kernel/git/daveh/devel.git/log/?h=x86/sgx
> 
> I'm planning to send this bunch up to Linus after 5.17-rc1 comes out.
> 
> Kristen, I really dug into the changelogs of your two patches to make it
> more clear that they are bugfix and stable@ material.  I'd appreciate
> some additional eyeballs there.

Thanks for the heads up, this actually fits perfectly my next weeks other
goals.

I'm implementing ECDSA attestation for Enarx next week (i.e. using AESMD).
I was planning to use this branch in any case.

I can combine that with enclaves that trigger backing storage (it can
host arbitarily sized WebAssembly programs). For those changes I'll do
testing both my own hardware (i5-9600KF) and also Icelake Server
(Platinum 8352Y).

If anything comes up, I'll post a fix directly, or if I get stuck I'll
rise up the issues here.

BR, Jarkko

  parent reply	other threads:[~2022-01-22 23:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21 19:57 Testing 5.17 bugfix material Dave Hansen
2022-01-22 19:15 ` Haitao Huang
2022-01-24 17:42   ` Jarkko Sakkinen
2022-01-24 17:55     ` Jarkko Sakkinen
2022-01-25  4:27       ` Haitao Huang
2022-01-22 23:41 ` Jarkko Sakkinen [this message]
2022-01-24 17:44 ` Accardi, Kristen C
2022-01-24 17:56   ` Jarkko Sakkinen
2022-01-24 20:59     ` Accardi, Kristen C
2022-01-25 12:06       ` Jarkko Sakkinen
2022-01-24 17:58 ` 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=YeyWMxWzvpEywbUx@iki.fi \
    --to=jarkko.sakkinen@iki.fi \
    --cc=dave.hansen@intel.com \
    --cc=jarkko.sakkinen@intel.com \
    --cc=kristen.c.accardi@intel.com \
    --cc=linux-sgx@vger.kernel.org \
    --cc=reinette.chatre@intel.com \
    --cc=tony.luck@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox