From: Chris Wright <chrisw@osdl.org>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Reserving a syscall number
Date: Wed, 27 Oct 2004 12:20:32 -0700 [thread overview]
Message-ID: <20041027122032.B14339@build.pdx.osdl.net> (raw)
In-Reply-To: <417FED6E.3010007@comcast.net>; from nigelenki@comcast.net on Wed, Oct 27, 2004 at 02:48:14PM -0400
* John Richard Moser (nigelenki@comcast.net) wrote:
> How would one go about having a specific syscall number reserved in
> entry.S? I'm exploring doing a kill inside the kernel from a detection
> done in userspace, which would allow the executable header of the binary
> to indicate whether the task should be killed or not; if it works, the
> changes will likely not go into mainline, but will still require a
> non-changing syscall index (assuming I understood the syscall manpage
> properly).
To reserve a syscall there needs to be some users and some eventual hope
of merging. The idea, btw, means anyone can specify the value in the
binary, so it could just as easily be done via prctl or something
similar that makes the out of tree patch easier to maintain. Although,
I don't actually see the value with the description above.
> On a side note, if a syscall doesn't exist, how would that be detected
> in userspace?
ENOSYS error.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2004-10-27 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 18:48 Reserving a syscall number John Richard Moser
2004-10-27 19:09 ` linux-os
2004-10-27 19:55 ` John Richard Moser
2004-10-27 19:20 ` Chris Wright [this message]
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=20041027122032.B14339@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.