mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: akpm <akpm@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: [PATCH] add syscalls.h
Date: Sun, 1 Feb 2004 22:22:54 -0800	[thread overview]
Message-ID: <20040201222254.39bc5b39.rddunlap@osdl.org> (raw)
In-Reply-To: <20040130163547.2285457b.rddunlap@osdl.org>

| Date: Tue, 27 Jan 2004 16:46:15 -0800
| From: Andrew Morton <akpm@osdl.org>
| Subject: Re: NGROUPS 2.6.2rc2
| 
| 
[snip]
| rant.  We have soooo many syscalls declared in .c files.  We had a bug due
| to this a while back.  Problem is, we have no anointed header in which to
| place them.  include/linux/syscalls.h would suit.  And unistd.h for
| arch-specific syscalls.  But that's not appropriate to this patch.


I am working on this.  Is anyone else?

I have parts 2.6.1-non-arch* ready for testing, I believe,
except that it will likely require more changes/additions.

I have begun on 2.6.1-arch* but still have a ways to go.

Caveats:
I have only patched 2.6.1.  I will update patches for 2.6.2-rc-current.
I have only tested by building allmodconfig on P4.
Have not test-booted yet.

Patch files for 2.6.1 are here:


http://developer.osdl.org/rddunlap/syscalls/2.6.1-arch-syscalls.diff
 drivers/macintosh/via-pmu.c |    2
 fs/compat.c                 |   14 ---
 include/linux/syscalls.h    |  173 ++++++++++++++++++++++++++++++++++++++++++++
 include/linux/sysctl.h      |    1
 init/do_mounts.h            |   15 ---
 init/do_mounts_devfs.c      |    6 -
 init/initramfs.c            |   12 ---
 kernel/compat.c             |   31 -------
 kernel/power/disk.c         |    3
 kernel/power/swsusp.c       |    3
 kernel/sysctl.c             |    2
 kernel/uid16.c              |   13 ---
 net/compat.c                |   23 -----
 13 files changed, 184 insertions(+), 114 deletions(-)


http://developer.osdl.org/rddunlap/syscalls/2.6.1-non-arch-syscalls.diff
 arch/alpha/kernel/osf_sys.c         |    3 --
 arch/ia64/ia32/ia32_ioctl.c         |    3 --
 arch/ia64/ia32/sys_ia32.c           |   26 ---------------------
 arch/mips/kernel/ioctl32.c          |    3 --
 arch/mips/kernel/irixioctl.c        |    4 ---
 arch/mips/kernel/linux32.c          |   13 ----------
 arch/mips/kernel/sysirix.c          |   15 ------------
 arch/parisc/hpux/ioctl.c            |    3 --
 arch/parisc/kernel/sys_parisc.c     |   14 -----------
 arch/parisc/kernel/sys_parisc32.c   |    7 -----
 arch/ppc64/kernel/ppc_ksyms.c       |    2 -
 arch/ppc64/kernel/sys_ppc32.c       |   44 +-----------------------------------
 arch/s390/kernel/compat_ioctl.c     |    3 --
 arch/s390/kernel/compat_linux.c     |   28 ----------------------
 arch/s390/kernel/sys_s390.c         |    3 --
 arch/sparc/kernel/sunos_ioctl.c     |    2 -
 arch/sparc/kernel/sys_sunos.c       |    5 ----
 arch/sparc64/kernel/sparc64_ksyms.c |    2 -
 arch/sparc64/kernel/sunos_ioctl32.c |    3 --
 arch/sparc64/kernel/sys_sparc.c     |    3 --
 arch/sparc64/kernel/sys_sparc32.c   |   25 --------------------
 arch/sparc64/kernel/sys_sunos32.c   |    3 --
 arch/sparc64/solaris/ioctl.c        |    3 --
 arch/sparc64/solaris/socksys.c      |    3 --
 arch/sparc64/solaris/timod.c        |    2 -
 arch/x86_64/ia32/ia32_ioctl.c       |    3 --
 arch/x86_64/ia32/sys_ia32.c         |   27 ----------------------
 arch/x86_64/kernel/x8664_ksyms.c    |    3 --
 include/asm-ia64/unistd.h           |    5 ++++
 include/asm-mips/unistd.h           |    5 ++++
 include/asm-parisc/unistd.h         |    4 +++
 include/asm-ppc/unistd.h            |    4 +++
 include/asm-ppc64/unistd.h          |    4 +++
 include/asm-sparc/unistd.h          |    5 ++++
 include/asm-sparc64/unistd.h        |    5 ++++
 include/asm-v850/unistd.h           |    4 +++
 include/asm-x86_64/unistd.h         |    4 +++
 37 files changed, 67 insertions(+), 228 deletions(-)


Do these look OK, as far as they go?  or am I way off?

--
~Randy


Haven't addressed these yet:

sys_brk
sys_wait*
sys_setuid/gid etc.
sys_init/delete_module
sys_ni_syscall
sys_get/setpriority
signal-related syscalls
rt-related syscalls
sys_execve
sys_ptrace
sys_newuname
schedule-related syscalls
sys_fadvise64_64
sys_nfsservctl
sys_kill
sys_setgroups
sys_sethost/domainname
sys_umask
sys_modify_ldt

       reply	other threads:[~2004-02-02  6:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040130163547.2285457b.rddunlap@osdl.org>
2004-02-02  6:22 ` Randy.Dunlap [this message]
2004-02-02  6:43   ` Andrew Morton
2004-02-03 20:29     ` Matt Mackall
2004-02-03 20:40       ` Richard B. Johnson
2004-02-03 21:18       ` Randy.Dunlap

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=20040201222254.39bc5b39.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=akpm@osdl.org \
    --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

all inboxes | Powered by JetHome®