From: ebiederm@xmission.com (Eric W. Biederman)
To: Christoph Lameter <clameter@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, oleg@tv-sign.ru,
mm-commits@vger.kernel.org
Subject: Re: + fork-allow-init-to-become-a-session-leader.patch added to -mm tree
Date: Thu, 09 Feb 2006 14:31:32 -0700 [thread overview]
Message-ID: <m1lkwk1aob.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0602081518580.5184@schroedinger.engr.sgi.com> (Christoph Lameter's message of "Wed, 8 Feb 2006 15:19:54 -0800 (PST)")
Christoph Lameter <clameter@engr.sgi.com> writes:
> On Wed, 8 Feb 2006 akpm@osdl.org wrote:
>
>> + if (unlikely(p->pid == 1)) {
>> + p->signal->tty = NULL;
>> + p->signal->leader = 1;
>> + p->signal->pgrp = 1;
>> + p->signal->session = 1;
>
> Would it not be better to do these special settings for init from
> init itself?
So if you mean from within the kernel context that is doable,
so long as we only have one process with pid == 1.
Although we may be able fix the kernel limitations in setsid().
For multiple pid == 1 case I don't know of another place in
the kernel I can possibly put this. I can't put it later
because there is no place later, and I can't put it earlier
or else my efforts would just get stomped.
So I did it this way so I don't have to come back and change it to
this next week. I'd love to have a better place to put this
code.
Eric
prev parent reply other threads:[~2006-02-09 21:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602082314.k18NEuN0017390@shell0.pdx.osdl.net>
2006-02-08 23:19 ` Christoph Lameter
2006-02-09 21:31 ` Eric W. Biederman [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=m1lkwk1aob.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=clameter@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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®