From: Chris Wright <chrisw@osdl.org>
To: "Søren Nøhr Christensen" <snc@cs.aau.dk>
Cc: linux-kernel@vger.kernel.org, umbrella@cs.aau.dk
Subject: Re: Syscall trouble
Date: Tue, 30 Nov 2004 13:03:20 -0800 [thread overview]
Message-ID: <20041130130320.J14339@build.pdx.osdl.net> (raw)
In-Reply-To: <200411301455.19143.snc@cs.aau.dk>; from snc@cs.aau.dk on Tue, Nov 30, 2004 at 02:55:19PM +0100
* Søren Nøhr Christensen (snc@cs.aau.dk) wrote:
<snip>
> +#define __NR_umb_set_child_restrictions 284
<snip>
> Any suggestions?
Don't do it this way. Use /proc/<pid>/attr/ interface if you only want
to handle creating restrictions within a process. If you're using it to
load your policy, then create a reasonable filesystem interface and do
it that way. This will be portable across versions and architectures
without allocating any syscalls.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
prev parent reply other threads:[~2004-11-30 21:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-30 13:55 Syscall trouble Søren Nøhr Christensen
2004-11-30 21:03 ` 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=20041130130320.J14339@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snc@cs.aau.dk \
--cc=umbrella@cs.aau.dk \
/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