public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: the arch/x86 maintainers <x86@kernel.org>,
	Stable Kernel <stable@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] xen: don't drop NX bit
Date: Fri, 20 Jun 2008 14:59:24 +0200	[thread overview]
Message-ID: <20080620125924.GK7439@elte.hu> (raw)
In-Reply-To: <4856E2D4.3020402@goop.org>


* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> When converting the pfn/mfn in a pagetable entry, make sure we mask 
> out the protection flags properly.  Formerly, this code was losing the 
> NX bit, and not dealing with extra Xen-defined software flags in ptes.
>
> Because NX is now enforced properly, we must put the hypercall page 
> into the .text segment so that it is executable.

applied all three fix patches to tip/x86/xen, thanks Jeremy.

i have also cherry-picked them into x86/urgent, to push v2.6.26-wards if 
they passes testing. The commits are [in that order]:

# x86/urgent: 4653938: xen: Use wmb instead of rmb in xen_evtchn_do_upcall().
# x86/urgent: 05345b0: xen: mask unwanted pte bits in __supported_pte_mask
# x86/urgent: ebb9cfe: xen: don't drop NX bit

	Ingo

      parent reply	other threads:[~2008-06-20 12:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-16 22:01 [PATCH 2/2] xen: don't drop NX bit Jeremy Fitzhardinge
2008-06-16 22:35 ` [stable] " Greg KH
2008-06-16 22:51   ` Jeremy Fitzhardinge
2008-06-16 23:37     ` Greg KH
2008-06-17 23:14       ` Chris Wright
2008-06-17 23:13   ` Chris Wright
2008-06-20 12:59 ` Ingo Molnar [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=20080620125924.GK7439@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.org \
    --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