From: Andre Tomt <andre@tomt.net>
To: linux-kernel@vger.kernel.org
Cc: Nuno Monteiro <nuno@itsari.org>,
Gianni Tedesco <gianni@scaramanga.co.uk>,
marcelo.tosatti@cyclades.com
Subject: Re: Local DoS attack on i386
Date: Tue, 15 Jun 2004 06:34:39 +0200 [thread overview]
Message-ID: <40CE7C5F.2070405@tomt.net> (raw)
In-Reply-To: <20040614142001.GA3032@hobbes.itsari.int>
Nuno Monteiro wrote:
> The same fix should be applied to 2.4. I'm running locally a very
> hacked version of 2.4.22 with it and it survives that crash.c program.
>
> Here's the diff. Marcelo, please merge.
>
>
> --- linux-2.4.27-pre5/include/asm-i386/i387.h~fix-x86-clear_fpu-macro 2004-06-14 15:12:13.909059344 +0100
> +++ linux-2.4.27-pre5/include/asm-i386/i387.h 2004-06-14 15:12:45.970185312 +0100
> @@ -34,7 +34,7 @@ extern void kernel_fpu_begin(void);
>
> #define clear_fpu( tsk ) do { \
> if ( tsk->flags & PF_USEDFPU ) { \
> - asm volatile("fwait"); \
> + asm volatile("fnclex ; fwait"); \
> tsk->flags &= ~PF_USEDFPU; \
> stts(); \
> } \
You're missing x86-64.
Complete patches are up at <http://tomt.net/kernel/clear_fpu/> - these
covers 2.4 and 2.6, plus i386 and x86-64.
But I guess Marcelo would want the x86-64 part to come through ak.
--
Cheers,
André Tomt
prev parent reply other threads:[~2004-06-15 4:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-12 9:59 new kernel bug Manuel Arostegui Ramirez
2004-06-12 12:33 ` Kalin KOZHUHAROV
2004-06-12 12:42 ` Manuel Arostegui Ramirez
2004-06-12 13:37 ` David Connolly
2004-06-12 15:08 ` Han Boetes
2004-06-12 15:08 ` Manuel Arostegui Ramirez
2004-06-14 13:58 ` Local DoS attack on i386 (was: new kernel bug) Gianni Tedesco
2004-06-14 14:05 ` Gianni Tedesco
2004-06-14 14:08 ` Manuel Arostegui Ramirez
2004-06-14 14:20 ` Nuno Monteiro
2004-06-14 14:59 ` Manuel Arostegui Ramirez
2004-06-15 4:34 ` Andre Tomt [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=40CE7C5F.2070405@tomt.net \
--to=andre@tomt.net \
--cc=gianni@scaramanga.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=nuno@itsari.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