Linux-Sgx Archive on lore.kernel.org
 help / color / Atom feed
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: Tue, 15 Oct 2019 00:03:17 +0300
Message-ID: <20191014210317.GU15552@linux.intel.com> (raw)
In-Reply-To: <20191010225530.26400-1-sean.j.christopherson@intel.com>

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.

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.

You already know that I applied 1/9 and 2/9 so please don't include
them.

/Jarkko

  parent reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 22:55 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 ` Jarkko Sakkinen [this message]
2019-10-16 16:39   ` [PATCH for_v23 0/4] x86/sgx: Fix add page bugs Sean Christopherson
2019-10-17 16:25     ` Jarkko Sakkinen

Reply instructions:

You may reply publically 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=20191014210317.GU15552@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

Linux-Sgx Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-sgx/0 linux-sgx/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-sgx linux-sgx/ https://lore.kernel.org/linux-sgx \
		linux-sgx@vger.kernel.org
	public-inbox-index linux-sgx

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-sgx


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git