From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Huang, Ying" <ying.huang@intel.com>
Cc: Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Andi Kleen <ak@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/6] x86: fix NX bit handling in change_page_attr
Date: Thu, 24 Jan 2008 23:32:25 -0800 [thread overview]
Message-ID: <47999089.5080609@goop.org> (raw)
In-Reply-To: <1201240493.15972.43.camel@caritas-dev.intel.com>
Huang, Ying wrote:
> This patch fixes a bug of change_page_attr/change_page_attr_addr on
> Intel i386/x86_64 CPUs. After changing page attribute to be
> executable with these functions, the page remains un-executable on
> Intel i386/x86_64 CPU. Because on Intel i386/x86_64 CPU, only if the
> "NX" bits of all three level page tables are cleared (PAE is enabled),
> the corresponding page is executable (refer to section 4.13.2 of Intel
> 64 and IA-32 Architectures Software Developer's Manual). So, the bug
> is fixed through clearing the "NX" bit of PMD when splitting the huge
> PMD.
>
> Signed-off-by: Huang Ying <ying.huang@intel.com>
>
> ---
> arch/x86/mm/pageattr.c | 1 +
> 1 file changed, 1 insertion(+)
>
> --- a/arch/x86/mm/pageattr.c
> +++ b/arch/x86/mm/pageattr.c
> @@ -124,6 +124,7 @@ static int split_large_page(pte_t *kpte,
> /*
> * Install the new, split up pagetable:
> */
> + pgprot_val(ref_prot) &= ~_PAGE_NX;
>
I don't think its a good idea to treat pgprot_val() as an lvalue - it
precludes it from being turned into an inline function. I know there
are numerous other places which do, but we should avoid making it worse.
J
next prev parent reply other threads:[~2008-01-25 7:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-25 5:54 [PATCH 1/6] x86: fix NX bit handling in change_page_attr Huang, Ying
2008-01-25 7:32 ` Jeremy Fitzhardinge [this message]
2008-01-25 8:46 ` Ingo Molnar
2008-01-25 10:32 ` Ingo Molnar
2008-01-25 20:05 ` Jeremy Fitzhardinge
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=47999089.5080609@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=ying.huang@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