From: Jarkko Sakkinen <jarkko@kernel.org>
To: Dave Hansen <dave.hansen@intel.com>
Cc: linux-sgx@vger.kernel.org,
Dave Hansen <dave.hansen@linux.intel.com>,
stable@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Jethro Beekman <jethro@fortanix.com>,
Sean Christopherson <seanjc@google.com>
Subject: Re: [PATCH v3] x86/sgx: Free backing memory after faulting the enclave page
Date: Sun, 20 Feb 2022 21:09:22 +0100 [thread overview]
Message-ID: <YhKf8gwdE8tyPTOA@iki.fi> (raw)
In-Reply-To: <bf6654d9-572b-3423-59a0-c17112f75792@intel.com>
On Sun, Feb 20, 2022 at 10:58:00AM -0800, Dave Hansen wrote:
> On 2/20/22 10:52, Jarkko Sakkinen wrote:
> >> Am I just all twisted around from looking at this code too much? Could
> >> you please take another look and send a new version of the patch?
> > Yeah, I will. It took me two weeks to make full remote attestation
> > implementation for SGX in Rust but at least I can confirm that all
> > the kernel bits work on that (and this will also help me to finish
> > the man page because it is pretty nasty to document it if you haven't
> > gone to the rabbit hole yourself).
> >
> > I'll prioritize now to get SGX2 patches tested with Enarx implementation
> > but this 2nd thing in my kernel queue.
>
> I really prioritize bug fixes over new features. New features can's
> really get merged until this gets fixed up.
Fair enough. In this case I was not exactly sure whether it is categorized
as bug or enhancement. Should I also put a fixes tag to this to the
original reclaimer code (since it has been like this since the epoch)?
BR, Jarkko
next prev parent reply other threads:[~2022-02-20 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-08 14:05 [PATCH v3] x86/sgx: Free backing memory after faulting the enclave page Jarkko Sakkinen
2022-01-13 6:08 ` Reinette Chatre
2022-01-14 21:25 ` Jarkko Sakkinen
2022-01-17 8:30 ` Jarkko Sakkinen
2022-01-24 17:17 ` Dave Hansen
2022-01-26 13:31 ` Jarkko Sakkinen
2022-01-27 7:01 ` Jarkko Sakkinen
2022-01-31 23:30 ` Dave Hansen
2022-02-20 18:52 ` Jarkko Sakkinen
2022-02-20 18:58 ` Dave Hansen
2022-02-20 20:09 ` Jarkko Sakkinen [this message]
2022-02-20 20:42 ` Jarkko Sakkinen
2022-02-22 0:15 ` 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=YhKf8gwdE8tyPTOA@iki.fi \
--to=jarkko@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jethro@fortanix.com \
--cc=linux-sgx@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).