From: Jamie Lokier <jamie@shareable.org>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: Do x86 NX and AMD prefetch check cause page fault infinite loop?
Date: Wed, 30 Jun 2004 15:23:51 +0100 [thread overview]
Message-ID: <20040630142351.GD29285@mail.shareable.org> (raw)
In-Reply-To: <200406300910.16396.vda@port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko wrote:
> > This can only happen when something branches to a page with PROT_EXEC
> > _not_ set, on a kernel which honours that, and the target address is a
> > prefetch instruction.
>
> Well. To be safe, just skip prefetch instruction, always.
> Hm. An attacker can supply us with whole gigabyte of
> prefetches back-to-back... Better skip all prefetches,
> with resheduling between every 1000 of them.
You could just skip one and return from the handler.
That's not a bad idea.
-- Jamie
prev parent reply other threads:[~2004-06-30 14:24 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
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 [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=20040630142351.GD29285@mail.shareable.org \
--to=jamie@shareable.org \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.