public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: qiyong <qiyong@fc-cn.com>
Cc: linux-kernel@vger.kernel.org, dhommel@gmail.com
Subject: Re: syscall: sys_promote
Date: Mon, 29 Aug 2005 13:29:27 +0100	[thread overview]
Message-ID: <1125318568.23946.15.camel@localhost.localdomain> (raw)
In-Reply-To: <4312870E.9000708@fc-cn.com>

On Llu, 2005-08-29 at 11:54 +0800, qiyong wrote:
> We can ignore it safely.  sys_promote is a different approach from 
> selinux.  sys_promote is to let sysadmin manually manipulate a running 
> process,

You can ignore the patch easily enough. Ignoring the locking doesn't
work because functionality like fork process counting, exec, and setuid
all make definite assumptions that are not safe to tamper without unless
you fix the uid locking.

Fixing it might be useful in some obscure cases anyway - POSIX threads
might benefit from it too, providing the functionality of changing all
thread uids at once isnt triggered for sensible threaded app behaviour.

  reply	other threads:[~2005-08-29 12:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-26  9:25 syscall: sys_promote Coywolf Qi Hunt
2005-08-26 11:02 ` Coywolf Qi Hunt
2005-08-26 15:19   ` Alan Cox
2005-08-29  3:54     ` qiyong
2005-08-29 12:29       ` Alan Cox [this message]
2005-08-29 16:15         ` Trond Myklebust
     [not found]         ` <a36005b505082908415d9202d5@mail.gmail.com>
2005-08-31  7:53           ` Qi Yong
2005-08-31  7:58         ` Qi Yong
2005-08-26 12:47 ` Erik Mouw
2005-08-29  3:55   ` qiyong
2005-08-29  7:53     ` Bernd Petrovitsch
2005-08-29  8:16       ` Coywolf Qi Hunt
2005-08-29  8:53         ` Bernd Petrovitsch

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=1125318568.23946.15.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=dhommel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiyong@fc-cn.com \
    /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