From: Carsten Langgaard <carstenl@mips.com>
To: linux-mips@oss.sgi.com
Subject: Bug in the _save_fp_context.
Date: Thu, 17 Jan 2002 14:34:37 +0100 [thread overview]
Message-ID: <3C46D2ED.9BCA458A@mips.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
I posted the following problem on the list almost a year ago, but it
still hasn't made into the SGI CVS.
I think there is a bug in the _save_fp_context function in
arch/mips/kernel/r4k_fpu.S
The problem is the following piece of code:
jr ra
.set nomacro
EX(sw t0,SC_FPC_EIR(a0))
.set macro
We do not handle entries in the __ex_table which is located in a branch
delay.
So we need to handle the situation where we take a page fault on an
instruction which is located in a brach delay slot, or we don't put the
"potential" faulting instruction in a delay slot.
This situation probably doesn't generally hit people since it hasn't
been fix yet, but if you try run something nasty like Crashme, you will
get hit by this problem.
I suggest the following patch.
/Carsten
--
_ _ ____ ___ Carsten Langgaard Mailto:carstenl@mips.com
|\ /|||___)(___ MIPS Denmark Direct: +45 4486 5527
| \/ ||| ____) Lautrupvang 4B Switch: +45 4486 5555
TECHNOLOGIES 2750 Ballerup Fax...: +45 4486 5556
Denmark http://www.mips.com
[-- Attachment #2: r4k_fpu.S.patch --]
[-- Type: text/plain, Size: 563 bytes --]
Index: arch/mips/kernel/r4k_fpu.S
===================================================================
RCS file: /cvs/linux/arch/mips/kernel/r4k_fpu.S,v
retrieving revision 1.12
diff -u -r1.12 r4k_fpu.S
--- arch/mips/kernel/r4k_fpu.S 2001/04/11 05:19:46 1.12
+++ arch/mips/kernel/r4k_fpu.S 2002/01/17 14:21:09
@@ -50,11 +50,10 @@
EX(sdc1 $f30,(SC_FPREGS+240)(a0))
EX(sw t1,SC_FPC_CSR(a0))
cfc1 t0,$0 # implementation/version
+ EX(sw t0,SC_FPC_EIR(a0))
jr ra
- .set nomacro
- EX(sw t0,SC_FPC_EIR(a0))
- .set macro
+ nop
END(_save_fp_context)
/*
next reply other threads:[~2002-01-17 14:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 13:34 Carsten Langgaard [this message]
[not found] ` <20020610114323.A25705@lucon.org>
2002-06-10 19:41 ` Bug in the _save_fp_context Carsten Langgaard
-- strict thread matches above, loose matches on Subject: below --
2001-03-19 14:07 Carsten Langgaard
2001-03-19 15:43 ` Kevin D. Kissell
2001-03-19 15:43 ` Kevin D. Kissell
2001-03-19 16:03 ` Kevin D. Kissell
2001-03-19 16:03 ` Kevin D. Kissell
2001-03-19 18:14 ` Jun Sun
2001-03-19 16:13 ` Carsten Langgaard
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=3C46D2ED.9BCA458A@mips.com \
--to=carstenl@mips.com \
--cc=linux-mips@oss.sgi.com \
/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