From: Jun Sun <jsun@mvista.com>
To: linux-mips@oss.sgi.com
Subject: a REALLY, REALLY nasty bug
Date: Wed, 25 Oct 2000 20:03:20 -0700 [thread overview]
Message-ID: <39F79EF8.9029AE6@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1494 bytes --]
Nasty degree - 3 days of tracking.
The symptom was pthread cannot be created. In the end the caller will
get a BUS error.
What exactly happened has to do with how registers are saved. Below
attached is the beginning part of sys_sigsuspend() function. It is easy
to see that s0 is saved into stack frame AFTER its modified. Next time
when process returns to userland, the s0 reg will be wrong!
So the bug is either
1) that we need to save s0 register in SAVE_SOME and not save it in
save_static; or that
2) we fix compiler so that it does not use s0 register in that case (it
does the same thing for sys_rt_sigsuspend)
I am sure Ralf will have something to say about it. :-) In any case, I
attached a patch for 1) fix.
Jun
------------
sys_sigsuspend(struct pt_regs regs)
{
8008e280: 27bdffc0 addiu $sp,$sp,-64
8008e284: afb00030 sw $s0,48($sp)
sigset_t *uset, saveset, newset;
save_static(®s);
8008e288: 27b00040 addiu $s0,$sp,64
8008e28c: afbf003c sw $ra,60($sp)
8008e290: afb20038 sw $s2,56($sp)
8008e294: afb10034 sw $s1,52($sp)
8008e298: afa40040 sw $a0,64($sp)
8008e29c: afa50044 sw $a1,68($sp)
8008e2a0: afa60048 sw $a2,72($sp)
8008e2a4: afa7004c sw $a3,76($sp)
8008e2a8: ae100058 sw $s0,88($s0)
8008e2ac: ae11005c sw $s1,92($s0)
.....
[-- Attachment #2: junk --]
[-- Type: text/plain, Size: 1032 bytes --]
diff -Nru linux/include/asm-mips/stackframe.h.orig linux/include/asm-mips/stackframe.h
--- linux/include/asm-mips/stackframe.h.orig Wed Oct 25 19:45:50 2000
+++ linux/include/asm-mips/stackframe.h Wed Oct 25 19:47:54 2000
@@ -49,7 +49,6 @@
#define save_static(frame) \
__asm__ __volatile__( \
- "sw\t$16,"__str(PT_R16)"(%0)\n\t" \
"sw\t$17,"__str(PT_R17)"(%0)\n\t" \
"sw\t$18,"__str(PT_R18)"(%0)\n\t" \
"sw\t$19,"__str(PT_R19)"(%0)\n\t" \
@@ -90,6 +89,7 @@
mfc0 v1, CP0_EPC; \
sw $7, PT_R7(sp); \
sw v1, PT_EPC(sp); \
+ sw $16, PT_R16(sp); \
sw $25, PT_R25(sp); \
sw $28, PT_R28(sp); \
sw $31, PT_R31(sp); \
next reply other threads:[~2000-10-26 3:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-26 3:03 Jun Sun [this message]
2000-10-26 23:38 ` a REALLY, REALLY nasty bug Ralf Baechle
2000-10-27 1:57 ` Jun Sun
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=39F79EF8.9029AE6@mvista.com \
--to=jsun@mvista.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