From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [git pull] x86 page fault checker
Date: Fri, 20 Feb 2009 16:50:36 +0100 [thread overview]
Message-ID: <20090220155036.GA3225@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0902201012220.29217@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> Ingo,
>
> This is not an urgent fix, but I based it on your urgent
> branch. The patch keeps the page fault handler from entering
> an infinite loop if the PMD does not match the PTE, and the
> PTE has the correct permissions but the PMD does not.
>
> With your latest change, this should not happen again. But if
> there's some other code out there that does have this bug, or
> if some future change creates it (never know with all the
> changes in virtualization) Perhaps it is still a good idea to
> have this check.
>
> This is not a fast path, and it should not hurt to have this
> level of paranoia.
>
> -- Steve
>
> Please pull the latest tip/x86/urgent tree, which can be found at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/x86/urgent
>
>
> Steven Rostedt (1):
> x86: check PMD in spurious_fault handler
>
> ----
> arch/x86/mm/fault.c | 13 ++++++++++++-
> 1 files changed, 12 insertions(+), 1 deletions(-)
> ---------------------------
> commit 8ef2333f1bdcc4a43cb37b1b5d8febf8e3d8cdc7
> Author: Steven Rostedt <srostedt@redhat.com>
> Date: Thu Feb 19 11:46:36 2009 -0500
>
> x86: check PMD in spurious_fault handler
>
> Impact: fix to prevent hard lockup on bad PMD permissions
>
> If the PMD does not have the correct permissions for a page access,
> but the PTE does, the spurious fault handler will mistake the fault
> as a lazy TLB transaction. This will result in an infinite loop of:
>
> fault -> spurious_fault check (pass) -> return to code -> fault
>
> This patch adds a check and a warn on if the PTE passes the permissions
> but the PMD does not.
>
> Signed-off-by: Steven Rostedt <srostedt@redhat.com>
>
> diff --git a/arch/x86/mm/fault.c b/arch/x86/mm/fault.c
> index c76ef1d..7b579a6 100644
> --- a/arch/x86/mm/fault.c
> +++ b/arch/x86/mm/fault.c
> @@ -455,6 +455,7 @@ static int spurious_fault(unsigned long address,
> pud_t *pud;
> pmd_t *pmd;
> pte_t *pte;
> + int ret;
>
> /* Reserved-bit violation or user access to kernel space? */
> if (error_code & (PF_USER | PF_RSVD))
> @@ -482,7 +483,17 @@ static int spurious_fault(unsigned long address,
> if (!pte_present(*pte))
> return 0;
>
> - return spurious_fault_check(error_code, pte);
> + ret = spurious_fault_check(error_code, pte);
> + if (!ret)
> + return 0;
> +
> + /*
> + * Make sure we have permissions in PMD
> + * If not, then there's a bug in the page tables.
> + */
> + ret = spurious_fault_check(error_code, (pte_t *) pmd);
> + WARN_ON(!ret);
> + return ret;
> }
i guess we could do this - but i'd rather have it as a
WARN_ONCE(), with some text - so that if it ever triggers it's
one surgical message.
Ingo
next prev parent reply other threads:[~2009-02-20 15:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-20 15:17 [git pull] x86 page fault checker Steven Rostedt
2009-02-20 15:50 ` Ingo Molnar [this message]
2009-02-20 16:00 ` Steven Rostedt
2009-02-20 17:37 ` [git pull v2] " Steven Rostedt
2009-02-20 17:52 ` Ingo Molnar
2009-02-20 17:58 ` Steven Rostedt
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=20090220155036.GA3225@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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