public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arkadiusz Miskiewicz <arekm@pld-linux.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Finalized FPU Crash Fix? [2.2.x]
Date: Thu, 17 Jun 2004 18:55:28 +0200	[thread overview]
Message-ID: <200406171855.28929.arekm@pld-linux.org> (raw)
In-Reply-To: <20040617160856.GA1470@brevity>

On Thursday 17 of June 2004 18:08, Josh Myer wrote:
> Hello everybody,
>
> Is there a general concensus that the one-liner in 2.6.7 is an
> appropriate fix for the FPU hang/crash bug?  I have several machines
> running 2.4.x which require that outside people have shell access.
> Needless to say, I'm somewhat nervous about this problem =)
And how this look in 2.2.x kernels? One guy here tells me that after running 
http://linuxreviews.org/news/2004-06-11_kernel_crash/index.html#toc1the 2.2 
kernel freezes.

Is such fix right one? 2.2.x doesn't crash with it.

Index: SOURCES/kernel-fwait-2.2.patch
diff -u /dev/null SOURCES/kernel-fwait-2.2.patch:1.1
--- /dev/null   Thu Jun 17 15:34:42 2004
+++ SOURCES/kernel-fwait-2.2.patch      Thu Jun 17 15:34:36 2004
@@ -0,0 +1,10 @@
+--- linux-2.2.26/include/asm-i386/processor.h~ Thu Jun 17 17:19:57 2004
++++ linux-2.2.26/include/asm-i386/processor.h  Thu Jun 17 17:32:36 2004
+@@ -426,6 +426,7 @@
+ 
+ #define clear_fpu(tsk) do { \
+       if (tsk->flags & PF_USEDFPU) { \
++              asm volatile("fnclex ; fwait"); \
+               tsk->flags &= ~PF_USEDFPU; \
+               stts(); \
+       } \
-- 
Arkadiusz Miśkiewicz     CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux

      reply	other threads:[~2004-06-17 16:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 16:08 Finalized FPU Crash Fix? Josh Myer
2004-06-17 16:55 ` Arkadiusz Miskiewicz [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=200406171855.28929.arekm@pld-linux.org \
    --to=arekm@pld-linux.org \
    --cc=linux-kernel@vger.kernel.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