All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Feng Wu <feng.wu@intel.com>,
	eddie.dong@intel.com, Ian.Campbell@citrix.com,
	jun.nakajima@intel.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v1 3/6] x86: Enable Supervisor Mode Execution Prevention (SMAP) for Xen
Date: Tue, 15 Apr 2014 15:26:53 +0100	[thread overview]
Message-ID: <534D41AD.3000002@citrix.com> (raw)
In-Reply-To: <534D5B5D02000078000090C1@nat28.tlf.novell.com>

On 15/04/14 15:16, Jan Beulich wrote:
>>>> On 15.04.14 at 16:09, <andrew.cooper3@citrix.com> wrote:
>> And having just sent this email, I further realise that functions like
>> show_page_walk() need protection against SMAP otherwise we will take a
>> recursive fault when trying to dump the error information from the first
>> fault.  I don't recall any of your other patches dealing with this.
> I don't follow: page table walks are done using map_domain_page(),
> which ought to not produce user mode accessible mappings. Or did
> you mean to say "may" instead of "will", and meant to do this just to
> be on the safe side?
>
> Jan
>

Hmm yes - in retrospect we shouldn't actually take faults from domain
mapped pages.

However for the safe side of things, we don't want to be taking
recursive faults in a panic scenario, so it might be a good idea to
preemptively stac() on terminal error paths.

~Andrew

      reply	other threads:[~2014-04-15 14:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-15 13:01 [PATCH v1 3/6] x86: Enable Supervisor Mode Execution Prevention (SMAP) for Xen Feng Wu
2014-04-15  5:36 ` Wu, Feng
2014-04-15 10:32 ` Andrew Cooper
2014-04-15 11:48   ` Jan Beulich
2014-04-15 13:46     ` Andrew Cooper
2014-04-16  2:20   ` Wu, Feng
2014-04-16  9:10     ` Andrew Cooper
2014-04-16  9:14       ` Jan Beulich
2014-04-15 14:00 ` Andrew Cooper
2014-04-15 14:09   ` Andrew Cooper
2014-04-15 14:16     ` Jan Beulich
2014-04-15 14:26       ` Andrew Cooper [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=534D41AD.3000002@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=eddie.dong@intel.com \
    --cc=feng.wu@intel.com \
    --cc=jun.nakajima@intel.com \
    --cc=xen-devel@lists.xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.