From: Harald Welte <laforge@gnumonks.org>
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] kill_proc_info_as_uid: don't use hardcoded constants
Date: Thu, 24 Nov 2005 21:48:50 +0100 [thread overview]
Message-ID: <20051124204850.GC31478@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <43847B85.4B97A782@tv-sign.ru>
[-- Attachment #1: Type: text/plain, Size: 1358 bytes --]
On Wed, Nov 23, 2005 at 05:24:05PM +0300, Oleg Nesterov wrote:
> Use symbolic names instead of hardcoded constants.
I'm more than happy with that. Seems like the original code in
check_kill_permission() was changed in a similar way after I made that
_as_uid() function.
I don't think that I am a person with any say in the signal.c code,but
in case of doubt:
Acked-by: Harald Welte <laforge@gnumonks.org>
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
>
> --- 2.6.15-rc2/kernel/signal.c~1_KUID 2005-11-22 19:35:52.000000000 +0300
> +++ 2.6.15-rc2/kernel/signal.c 2005-11-23 19:17:35.000000000 +0300
> @@ -1163,8 +1163,7 @@ int kill_proc_info_as_uid(int sig, struc
> ret = -ESRCH;
> goto out_unlock;
> }
> - if ((!info || ((unsigned long)info != 1 &&
> - (unsigned long)info != 2 && SI_FROMUSER(info)))
> + if ((info == SEND_SIG_NOINFO || (!is_si_special(info) && SI_FROMUSER(info)))
> && (euid != p->suid) && (euid != p->uid)
> && (uid != p->suid) && (uid != p->uid)) {
> ret = -EPERM;
--
- Harald Welte <laforge@gnumonks.org> http://gnumonks.org/
============================================================================
"Privacy in residential applications is a desirable marketing option."
(ETSI EN 300 175-7 Ch. A6)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-11-24 20:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 14:24 Oleg Nesterov
2005-11-24 20:48 ` Harald Welte [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=20051124204850.GC31478@sunbeam.de.gnumonks.org \
--to=laforge@gnumonks.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
/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®