From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kill_something_info: misc cleanups
Date: Sat, 16 Dec 2006 16:10:01 -0700 [thread overview]
Message-ID: <m1psajtp2u.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061216200510.GA5535@tv-sign.ru> (Oleg Nesterov's message of "Sat, 16 Dec 2006 23:05:10 +0300")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> On top of
> signal-rewrite-kill_something_info-so-it-uses-newer-helpers.patch
>
> - Factor out sending PIDTYPE_PGID wide signals.
>
> - Use is_init(p) instead of "p->pid > 1". We don't hash idle threads anymore,
> no need to worry about p->pid == 0.
I do not believe is_init is the proper function here. In the presence
of multiple pid namespaces the intention is for is_init to catch all of
the special handling (except signal behavior) for the init process.
That way when we have multiple processes with pid == 1 we know which
one we care about.
> - Use "p != current->group_leader" instead of "p->tgid != current->tgid",
> saves one dereference and kills yet another direct pid_t usage.
Makes sense as you have to be a group_leader to be on the task list.
> - Simplify return value calculation for "pid == -1" case, remove "retval"
> variable.
>
> No functional changes.
Looks sane.
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Eric
next prev parent reply other threads:[~2006-12-16 23:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-16 20:05 Oleg Nesterov
2006-12-16 23:10 ` Eric W. Biederman [this message]
2006-12-17 0:37 ` Oleg Nesterov
2006-12-17 1:09 ` Eric W. Biederman
2006-12-17 10:18 ` Christoph Hellwig
2006-12-17 11:22 ` Eric W. Biederman
2006-12-17 14:40 ` Oleg Nesterov
2006-12-18 13:09 ` Eric W. Biederman
2006-12-18 21:24 ` Oleg Nesterov
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=m1psajtp2u.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--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®