From: qiyong <qiyong@fc-cn.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, dhommel@gmail.com
Subject: Re: syscall: sys_promote
Date: Mon, 29 Aug 2005 11:54:54 +0800 [thread overview]
Message-ID: <4312870E.9000708@fc-cn.com> (raw)
In-Reply-To: <1125069558.4958.83.camel@localhost.localdomain>
Alan Cox wrote:
>On Gwe, 2005-08-26 at 19:02 +0800, Coywolf Qi Hunt wrote:
>
>
>>>3) admins can `promote' a suspect process instead of killing it.
>>>
>>>Is it also generally useful in practice? Thoughts?
>>>
>>>
>
>The locking is wrong. At the moment the entire kernel assumes that a
>process uid is not changed by anyone else. After you've implemented uid
>locking/refcounting for tasks you can add the syscall but until then its
>not a good idea. I don't think its a good idea anyway - selinux can do
>far more useful things.
>
Indeed. "Also it's not obvious that locking can be done right (or that
anybody cares). "
We can ignore it safely. sys_promote is a different approach from
selinux. sys_promote is to let sysadmin manually manipulate a running
process,
next prev parent reply other threads:[~2005-08-29 3:55 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 [this message]
2005-08-29 12:29 ` Alan Cox
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=4312870E.9000708@fc-cn.com \
--to=qiyong@fc-cn.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dhommel@gmail.com \
--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 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.