Skip to contentSkip to conversation

- UML - don't rule out syscall_nr == 0

PATCH In review Jeff Dike 1 participant 1 message Nov 12, 2004 User-mode Linux (UML)

lore
Share & tools
lore

Jeff Dike

author
#0 lore raw

PATCH 3/11 - UML - don't rule out syscall_nr == 0

Quoted 1 line

From Bodo Stroesser - Change the valid system call numbers to reflect the

possibility that we could have __NR_restart_syscall.

arch/um/kernel/skas/process.c +1 -1
Index: 2.6.9/arch/um/kernel/skas/process.c
===================================================================
@@ -64,7 +64,7 @@
 
 	syscall_nr = PT_SYSCALL_NR(regs->skas.regs);
 	UPT_SYSCALL_NR(regs) = syscall_nr;
-	if(syscall_nr < 1){
+	if(syscall_nr < 0){
 		relay_signal(SIGTRAP, regs);
 		return;
 	}
arch/um/kernel/tt/syscall_user.c +2 -1
Index: 2.6.9/arch/um/kernel/tt/syscall_user.c
===================================================================
@@ -63,7 +63,8 @@
 	regs = TASK_REGS(task);
 	UPT_SYSCALL_NR(regs) = syscall;
 
-	if(syscall < 1) return(0);
+	if(syscall < 0)
+		return(0);
 
 	if((syscall != __NR_sigreturn) &&
 	   ((unsigned long *) PT_IP(proc_regs) >= &_stext) &&