Skip to contentSkip to conversation

mips64 scall_o32.S fixes?

DISCUSSION Kip Walker 1 participant 1 message Mar 7, 2003 MIPS

lore
Share & tools
lore

Kip Walker

author
#0 lore raw

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