From: Ingo Molnar <mingo@elte.hu>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@redhat.com>,
the arch/x86 maintainers <x86@kernel.org>,
Stable Kernel <stable@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] xen: Check NX state before setting up GDT mapping
Date: Wed, 23 Sep 2009 14:35:27 +0200 [thread overview]
Message-ID: <20090923123527.GB19385@elte.hu> (raw)
In-Reply-To: <4AB7EC1D.5010102@goop.org>
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Hi Ingo,
>
> This is a little followup fix to the previous Xen stack-protector
> patches to deal with the case of a 64-bit processor without NX support
> (either old Intel or disabled in BIOS). Before creating the mapping for
> the GDT we need to make sure that NX is actually supported or the
> processor will fault on us.
>
> This ends up making mm/init.o non-stack-protected. Given that this file
> has some fairly complex functions with local arrays, I've made an
> additional change to move the NX setup into its own file to limit the
> non-stack-protected code. I added it as a later delta so that the pure
> bugfix can be applied to stable, and the cleanup can go on top into
> mainline.
>
> Thanks,
> J
>
> The following changes since commit 79b520e87e1214cfa107bdc8528b5d6c055a8b82:
> Linus Torvalds (1):
> Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git bugfix
>
> Jeremy Fitzhardinge (2):
> xen: check EFER for NX before setting up GDT mapping
> x86: split NX setup into separate file to limit unstack-protected code
>
> arch/x86/include/asm/pgtable_types.h | 1 +
> arch/x86/mm/Makefile | 3 +-
> arch/x86/mm/init.c | 63 -------------------------------
> arch/x86/mm/setup_nx.c | 69 ++++++++++++++++++++++++++++++++++
> arch/x86/xen/enlighten.c | 10 ++--
> 5 files changed, 77 insertions(+), 69 deletions(-)
> create mode 100644 arch/x86/mm/setup_nx.c
Pulled, thanks Jeremy!
Ingo
next prev parent reply other threads:[~2009-09-23 12:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-21 21:11 Jeremy Fitzhardinge
2009-09-23 12:35 ` Ingo Molnar [this message]
2009-09-23 12:36 ` Ingo Molnar
2009-09-23 19:03 ` Jeremy Fitzhardinge
2009-09-23 19:13 ` Ingo Molnar
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=20090923123527.GB19385@elte.hu \
--to=mingo@elte.hu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=stable@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.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
all inboxes | Powered by JetHome®