mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kwl02r <kwl02r@ecs.soton.ac.uk>
To: linux-kernel@vger.kernel.org
Subject: strange new system call problems
Date: Fri, 06 Aug 2004 10:56:09 +0100	[thread overview]
Message-ID: <411355B9.9060304@ecs.soton.ac.uk> (raw)

    Hiya,

    I am running the Redhat9 with kernel-2.4.20-8. I added four new 
system calls for my application program.
    At file /asm/unistd.h, I added my system calls definition as following.
   
    #define __NR_set_tid_address    258 /* last system call defined by 
system*/

   #define __NR_mysystemcall1  259  /* my first system call*/
   #define __NR_mysystemcall2  260  /* my second system call*/
   #define __NR_mysystemcall3  261  /* my third system call*/
   #define __NR_mysystemcall4  262  /* my forth system call*/

   After this , I changed the linux/arch/i386/entry.S as following.
  . long SYMBOL_NAME(sys_mysystemcall1)             /* 259 system call */
  .long SYMBOL_NAME(sys_mysystemcall2)              /* 260 system call */
  .long SYMBOL_NAME(sys_mysystemcall3)              /* 261 system call */
  .long SYMBOL_NAME(sys_mysystemcall4)              /* 262 system call */

   When I compilered a new kernel, there was no any error messages.
   But only the new system call 259 was working. The rest of three 
(260-262) did not response
   anything. If I changed the position of system calls (259->260 and 
260->259), still the 259 had
   response. Anyway, only the new system call at the 259 position was 
working. What is wrong?
   Other questions are:
   (1) Is it correct that I add my new definitions at 
/linux/asm/unistd.h? There is another file under
         /linux/asm-i386/unistd.h
   (2) At entry.S, do I need to change codes following for my new system 
calls? How to change ?
       
       .rept NR_syscalls-(.-sys_call_table)/4
               .long SYMBOL_NAME(sys_ni_syscall)
        .endr

Thanks



   


 

   


                 reply	other threads:[~2004-08-06  9:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=411355B9.9060304@ecs.soton.ac.uk \
    --to=kwl02r@ecs.soton.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome