* mips64 scall_o32.S fixes?
@ 2003-03-07 19:27 Kip Walker
0 siblings, 0 replies; only message in thread
From: Kip Walker @ 2003-03-07 19:27 UTC (permalink / raw)
To: Ralf Baechle, linux-mips
I assume sys32_syscall should only allow o32 syscalls? So the #defines
being used were wrong. And MAX_SYSCALL_NO, although unused, seems to
have the wrong thing in it.
Any disagreement?
Kip
Index: arch/mips64/kernel/scall_o32.S
===================================================================
RCS file: /home/cvs/linux/arch/mips64/kernel/scall_o32.S,v
retrieving revision 1.48.2.26
diff -u -r1.48.2.26 scall_o32.S
--- arch/mips64/kernel/scall_o32.S 7 Mar 2003 01:22:48 -0000
1.48.2.26
+++ arch/mips64/kernel/scall_o32.S 7 Mar 2003 19:26:36 -0000
@@ -23,7 +23,7 @@
#include <asm/sysmips.h>
/* Highest syscall used of any syscall flavour */
-#define MAX_SYSCALL_NO __NR_Linux32 + __NR_Linux32_syscalls
+#define MAX_SYSCALL_NO __NR_N32_Linux + __NR_N32_Linux_syscalls
.align 5
NESTED(handle_sys, PT_SIZE, sp)
@@ -263,7 +263,7 @@
LEAF(sys32_syscall)
ld t0, PT_R29(sp) # user sp
- sltu v0, a0, __NR_Linux + __NR_Linux_syscalls + 1
+ sltu v0, a0, __NR_O32_Linux + __NR_O32_Linux_syscalls + 1
beqz v0, enosys
dsll v0, a0, 3
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-03-07 19:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-03-07 19:27 mips64 scall_o32.S fixes? Kip Walker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox