From: Robert Love <rml@tech9.net>
To: marcelo@conectiva.com.br
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] 2.4: reserve syscalls from 2.5
Date: 10 Apr 2002 16:40:22 -0400 [thread overview]
Message-ID: <1018471223.6524.83.camel@phantasy> (raw)
Marcelo,
The following patch reserves syscall numbers 239 through 242 which are
the calls to date added to 2.5. I just set them to sys_ni_syscall and
note which 2.5 function they correspond to.
Patch is against 2.5.19-pre6, please apply.
Robert Love
diff -urN linux-2.4.19-pre6/arch/i386/kernel/entry.S linux/arch/i386/kernel/entry.S
--- linux-2.4.19-pre6/arch/i386/kernel/entry.S Fri Apr 5 14:53:39 2002
+++ linux/arch/i386/kernel/entry.S Wed Apr 10 16:28:17 2002
@@ -635,6 +635,10 @@
.long SYMBOL_NAME(sys_ni_syscall) /* reserved for lremovexattr */
.long SYMBOL_NAME(sys_ni_syscall) /* reserved for fremovexattr */
.long SYMBOL_NAME(sys_tkill)
+ .long SYMBOL_NAME(sys_ni_syscalls) /* reserved for sendfile64 */
+ .long SYMBOL_NAME(sys_ni_syscalls) /* 240 reserved for futex */
+ .long SYMBOL_NAME(sys_ni_syscalls) /* reserved for sched_setaffinity */
+ .long SYMBOL_NAME(sys_ni_syscalls) /* reserved for sched_getaffinity */
.rept NR_syscalls-(.-sys_call_table)/4
.long SYMBOL_NAME(sys_ni_syscall)
diff -urN linux-2.4.19-pre6/include/asm-i386/unistd.h linux/include/asm-i386/unistd.h
--- linux-2.4.19-pre6/include/asm-i386/unistd.h Fri Apr 5 14:53:56 2002
+++ linux/include/asm-i386/unistd.h Wed Apr 10 16:21:00 2002
@@ -242,8 +242,11 @@
#define __NR_removexattr 235
#define __NR_lremovexattr 236
#define __NR_fremovexattr 237
-
#define __NR_tkill 238
+#define __NR_sendfile64 239
+#define __NR_futex 240
+#define __NR_sched_setaffinity 241
+#define __NR_sched_getaffinity 242
/* user-visible error numbers are in the range -1 - -124: see <asm-i386/errno.h> */
next reply other threads:[~2002-04-10 20:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 20:40 Robert Love [this message]
2002-04-11 3:53 ` [PATCH] 2.4: reserve syscalls from 2.5 Robert Love
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=1018471223.6524.83.camel@phantasy \
--to=rml@tech9.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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