From: Jamie Lokier <jamie@shareable.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>
Subject: Re: Do x86 NX and AMD prefetch check cause page fault infinite loop?
Date: Thu, 1 Jul 2004 16:04:30 +0100 [thread overview]
Message-ID: <20040701150430.GB5114@mail.shareable.org> (raw)
In-Reply-To: <20040701063237.GA16166@elte.hu>
Ingo Molnar wrote:
> -#ifdef CONFIG_X86_PAE
> - {
> - pgd_t *pgd;
> - pmd_t *pmd;
> - pgd = init_mm.pgd + pgd_index(address);
> - if (pgd_present(*pgd)) {
> - pmd = pmd_offset(pgd, address);
> - if (pmd_val(*pmd) & _PAGE_NX)
> - printk(KERN_CRIT "kernel tried to access NX-protected page - exploit attempt? (uid: %d)\n", current->uid);
> - }
> - }
> -#endif
> + if (nx_enabled && (error_code & 16))
> + printk(KERN_CRIT "kernel tried to execute NX-protected page - exploit attempt? (uid: %d)\n", current->uid);
According to AMD's manual, bit 4 of error_code means the fault was due
to an instruction fetch. It doesn't imply that it's an NX-protected
page: it might be a page not present fault instead. (The manual
doesn't spell that out, it just says the bit is set when it's an
instruction fetch).
Just so you realise that the above code fragments aren't logically
equivalent.
-- Jamie
next prev parent reply other threads:[~2004-07-01 15:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 1:38 Do x86 NX and AMD prefetch check cause page fault infinite loop? Jamie Lokier
2004-06-30 5:50 ` Ingo Molnar
2004-06-30 14:21 ` Jamie Lokier
2004-06-30 14:38 ` Jamie Lokier
2004-07-01 1:48 ` Jamie Lokier
2004-07-01 6:32 ` Ingo Molnar
2004-07-01 15:04 ` Jamie Lokier [this message]
2004-07-02 7:15 ` Ingo Molnar
2004-07-02 8:50 ` [patch] i386 nx prefetch fix & cleanups, 2.6.7-mm5 Ingo Molnar
2004-06-30 6:10 ` Do x86 NX and AMD prefetch check cause page fault infinite loop? Denis Vlasenko
2004-06-30 14:23 ` Jamie Lokier
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=20040701150430.GB5114@mail.shareable.org \
--to=jamie@shareable.org \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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