From: "Jarkko Sakkinen" <jarkko@kernel.org>
To: "Jo Van Bulck" <jo.vanbulck@cs.kuleuven.be>,
<linux-sgx@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <dave.hansen@linux.intel.com>
Subject: Re: [PATCH 0/4] selftests/sgx: Harden test enclave
Date: Fri, 28 Jul 2023 18:54:39 +0000 [thread overview]
Message-ID: <CUE17WOKP8HH.39KZQV0H8IRBV@seitikki> (raw)
In-Reply-To: <707e662f-5aed-ef86-a2e3-dda3959d6f7d@cs.kuleuven.be>
On Mon Jul 24, 2023 at 10:46 AM UTC, Jo Van Bulck wrote:
> On 22.07.23 20:10, Jarkko Sakkinen wrote:
> > This code is not meant for production. I implemented it specifically for
> > kselftest, and that is exactly its scope.
>
> I see, makes sense. As per Dave's suggestion, I'll see if I can submit a
> proposed minimal patch to remove any existing sanitization code that is
> not necessary for kselftest (eg register cleansing) and avoid any
> misguided impressions of the test enclave being representative.
>
> > I'm not sure what is "correct" behavior in the context of a kselftest
> > instance.
>
> True. But at least when defining "correct" as passing the selftests,
> then I think it makes sense to merge the compiler optimization fixes. As
> the existing code clearly emits wrong assembly that breaks the selftests
> when switching optimization levels (which may always also be
> incorporated by default in future gcc versions or other compilers like
> clang).
>
> Thus, I'll separate this out and submit another patch to ensure
> correctness with compiler optimizations only.
>
> Best,
> Jo
It should be relatively easy to relicense the code as most of the
commits have Intel copyright.
Personally I would not mind because that would give opportunity for
code that I wrote to have a wider audience but it needs to be forked
with some other license first.
BR, Jarkko
next prev parent reply other threads:[~2023-07-28 18:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 14:24 [PATCH 0/4] selftests/sgx: Harden test enclave Jo Van Bulck
2023-07-19 14:24 ` [PATCH 1/4] selftests/sgx: Harden test enclave ABI Jo Van Bulck
2023-07-20 17:27 ` Jarkko Sakkinen
2023-07-20 19:14 ` Jo Van Bulck
2023-07-19 14:24 ` [PATCH 2/4] selftests/sgx: Store base address and size in test enclave Jo Van Bulck
2023-07-20 17:29 ` Jarkko Sakkinen
2023-07-20 19:18 ` Jo Van Bulck
2023-07-19 14:24 ` [PATCH 3/4] selftests/sgx: Harden test enclave API Jo Van Bulck
2023-07-20 17:32 ` Jarkko Sakkinen
2023-07-20 19:34 ` Jo Van Bulck
2023-07-19 14:25 ` [PATCH 4/4] selftests/sgx: Fix compiler optimizations in test enclave Jo Van Bulck
2023-07-20 17:25 ` [PATCH 0/4] selftests/sgx: Harden " Jarkko Sakkinen
2023-07-20 19:12 ` Jo Van Bulck
2023-07-20 19:56 ` Dave Hansen
2023-07-20 20:57 ` Jo Van Bulck
2023-07-22 18:10 ` Jarkko Sakkinen
2023-07-24 10:46 ` Jo Van Bulck
2023-07-28 18:54 ` Jarkko Sakkinen [this message]
2023-08-07 6:06 ` Jo Van Bulck
2023-08-07 11: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=CUE17WOKP8HH.39KZQV0H8IRBV@seitikki \
--to=jarkko@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=jo.vanbulck@cs.kuleuven.be \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox