From: Kirill Korotaev <dev@sw.ru>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/3] pidhash: don't use zero pids
Date: Tue, 31 Jan 2006 09:12:07 +0300 [thread overview]
Message-ID: <43DEFFB7.6010404@sw.ru> (raw)
In-Reply-To: <m1r76p5u7m.fsf@ebiederm.dsl.xmission.com>
Hello Oleg,
I had quite the same comment, but had no time to check it.
I can't understand what problem do you solve, or just making code
cleaner (from your point of view)?
For me it was quite natural that pid=0 is used by idle, and I'm very
suspicuos about such changes.
Kirill
> Oleg Nesterov <oleg@tv-sign.ru> writes:
>
>> daemonize() calls set_special_pids(1,1), while init and
>> kernel threads spawned from init/main.c:init() run with
>> 0,0 special pids. This patch changes INIT_SIGNALS() so
>> that that they run with ->pgrp == ->session == 1 also.
>>
>> This patch relies on fact that swapper's pid == 1.
>>
>> Now we never use pid == 0 in kernel/pid.c.
>
> This changes what is visible to user space, for the case
> where we are not a member of a session of a process group.
>
> By hashing the values these non-groups become available to
> user space. Which I find disturbing. Before I can comment
> further I need to see if there are any well defined semantics
> for processes that are not part of a session or a process
> group. If there are well defined semantics we have just
> broken user space.
>
> Eric
>
next prev parent reply other threads:[~2006-01-31 6:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-30 11:06 Oleg Nesterov
2006-01-30 20:36 ` Eric W. Biederman
2006-01-31 6:12 ` Kirill Korotaev [this message]
2006-01-31 10:28 ` Oleg Nesterov
2006-01-31 15:02 ` Eric W. Biederman
2006-01-30 22:43 ` Eric W. Biederman
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=43DEFFB7.6010404@sw.ru \
--to=dev@sw.ru \
--cc=akpm@osdl.org \
--cc=ebiederm@xmission.com \
--cc=jdike@addtoit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
Powered by JetHome