From: Jeff Dike <jdike@addtoit.com>
To: "Stroesser, Bodo" <Bodo.Stroesser@fujitsu-siemens.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: Re: [uml-devel] Minor problems with interrupted systemcalls
Date: Fri, 24 Sep 2004 17:32:27 -0400 [thread overview]
Message-ID: <200409242132.i8OLWRZX003935@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Wed, 22 Sep 2004 19:12:37 +0200." <8B6FF516CBA0194AB0996705076B02520F7C38@ABGEX01E.abg.fsc.net>
Change the valid system call numbers to reflect the possibility that we could
have __NR_restart_syscall.
Index: 2.6.9-rc/arch/um/kernel/skas/process.c
===================================================================
--- 2.6.9-rc.orig/arch/um/kernel/skas/process.c 2004-09-24 16:04:02.000000000 -0400
+++ 2.6.9-rc/arch/um/kernel/skas/process.c 2004-09-24 16:04:16.000000000 -0400
@@ -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;
}
Index: 2.6.9-rc/arch/um/kernel/tt/syscall_user.c
===================================================================
--- 2.6.9-rc.orig/arch/um/kernel/tt/syscall_user.c 2004-09-24 16:04:02.000000000 -0400
+++ 2.6.9-rc/arch/um/kernel/tt/syscall_user.c 2004-09-24 16:04:49.000000000 -0400
@@ -56,7 +56,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) &&
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-24 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 17:12 [uml-devel] Minor problems with interrupted systemcalls Stroesser, Bodo
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike [this message]
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
2004-09-24 21:32 ` Jeff Dike
-- strict thread matches above, loose matches on Subject: below --
2004-09-29 16:34 Stroesser, Bodo
2004-09-29 21:10 ` Jeff Dike
2004-09-20 10:06 Stroesser, Bodo
2004-09-21 17:31 ` BlaisorBlade
2004-09-17 17:46 Stroesser, Bodo
2004-09-18 16:17 ` BlaisorBlade
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=200409242132.i8OLWRZX003935@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=Bodo.Stroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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