From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Sean Christopherson <sean.j.christopherson@intel.com>
Cc: linux-sgx@vger.kernel.org
Subject: Re: [PATCH for_v23 0/4] x86/sgx: Fix add page bugs
Date: Thu, 17 Oct 2019 19:25:19 +0300 [thread overview]
Message-ID: <20191017162519.GC6667@linux.intel.com> (raw)
In-Reply-To: <20191016163914.GD5866@linux.intel.com>
On Wed, Oct 16, 2019 at 09:39:14AM -0700, Sean Christopherson wrote:
> On Tue, Oct 15, 2019 at 12:03:17AM +0300, Jarkko Sakkinen wrote:
> > On Thu, Oct 10, 2019 at 03:55:26PM -0700, Sean Christopherson wrote:
> > > Three bug fixes in the add page flow, along with a related enhancement.
> > > Note, patch 4/4 is effectively a revert.
> > >
> > > Sean Christopherson (4):
> > > x86/sgx: Pass EADD the kernel's virtual address for the source page
> > > x86/sgx: Check the validity of the source page address for EADD
> > > x86/sgx: Fix EEXTEND error handling
> > > x86/sgx: Drop mmap_sem before EEXTENDing an enclave page
> > >
> > > arch/x86/kernel/cpu/sgx/ioctl.c | 46 ++++++++++++++++++---------------
> > > 1 file changed, 25 insertions(+), 21 deletions(-)
> >
> > So, which one should be merged first. This or v2 of the other series.
>
> Shouldn't matter.
>
> > Can you send a single "for-v23 fixes" series with everything needed just
> > so that there is no room guess work? You can call v3 of the series that
> > you first started.
>
> Will do, I'll get it sent out today.
Thank you. I'll start to go through and merging (have the patch set
now).
Rather than send any new versions lets just discuss if there is
something that looks weird and I'll either pick the patch unmodified or
do whatever mods needs depending on the resolution.
/Jarkko
prev parent reply other threads:[~2019-10-17 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 22:55 [PATCH for_v23 0/4] x86/sgx: Fix add page bugs Sean Christopherson
2019-10-10 22:55 ` [PATCH for_v23 1/4] x86/sgx: Pass EADD the kernel's virtual address for the source page Sean Christopherson
2019-10-10 22:55 ` [PATCH for_v23 2/4] x86/sgx: Check the validity of the source page address for EADD Sean Christopherson
2019-10-10 22:55 ` [PATCH for_v23 3/4] x86/sgx: Fix EEXTEND error handling Sean Christopherson
2019-10-10 22:55 ` [PATCH for_v23 4/4] x86/sgx: Drop mmap_sem before EEXTENDing an enclave page Sean Christopherson
2019-10-14 21:03 ` [PATCH for_v23 0/4] x86/sgx: Fix add page bugs Jarkko Sakkinen
2019-10-16 16:39 ` Sean Christopherson
2019-10-17 16:25 ` Jarkko Sakkinen [this message]
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=20191017162519.GC6667@linux.intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=linux-sgx@vger.kernel.org \
--cc=sean.j.christopherson@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;
as well as URLs for NNTP newsgroup(s).