From: ebiederm@xmission.com (Eric W. Biederman)
To: Roland McGrath <roland@redhat.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>,
Andrew Morton <akpm@linux-foundation.org>,
Davide Libenzi <davidel@xmailserver.org>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Robin Holt <holt@sgi.com>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [RFC, PATCH 1/3] introduce SYS_CLONE_MASK
Date: Mon, 09 Apr 2007 10:20:27 -0600 [thread overview]
Message-ID: <m11wit34fo.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070409020600.6338BD82F4@pipsqueak.sf.frob.com> (Roland McGrath's message of "Sun, 8 Apr 2007 19:06:00 -0700 (PDT)")
Roland McGrath <roland@redhat.com> writes:
> I concur with Eric's assessment. Adding new magic bits to the generic
> clone path seems like a poor way to cope with kernel threads. I think
> it's better if kernel thread setup gets less like normal user process
> setup. I also agree with Eric that PPID of 0 is a very natural way for
> kernel threads to be displayed. We need to know more about the nature
> of the compatibility issue in procps to judge whether there is good
> reason to avoid changing it.
I just investigated the procps issue. Using init_task as the parent
nothing sticks out as being wrong in /proc.
Further when I modified pstree to accept 0 as it's starting pid (from
which all else would be rooted). All of the kernel threads showed up.
So if anything I it is a feature that kernel threads don't show up
by default in pstree (when PPID == 0). It isn't a subtle kernel bug.
Eric
next prev parent reply other threads:[~2007-04-09 16:23 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-08 15:53 [RFC, PATCH 1/3] introduce SYS_CLONE_MASK Oleg Nesterov
2007-04-08 16:19 ` Eric W. Biederman
2007-04-08 16:57 ` Oleg Nesterov
2007-04-09 1:05 ` Eric W. Biederman
2007-04-09 2:06 ` Roland McGrath
2007-04-09 16:20 ` Eric W. Biederman [this message]
2007-04-09 17:30 ` Robin Holt
2007-04-10 0:35 ` Eric W. Biederman
2007-04-10 9:56 ` Robin Holt
2007-04-09 9:06 ` Oleg Nesterov
2007-04-09 10:43 ` Robin Holt
2007-04-09 14:36 ` Eric W. Biederman
2007-04-09 14:52 ` Robin Holt
2007-04-10 15:47 ` Jan Engelhardt
2007-04-10 18:20 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 2:59 Albert Cahalan
2007-05-29 4:57 ` Eric W. Biederman
2007-05-29 3:23 Albert Cahalan
2007-05-29 4:53 ` Eric W. Biederman
2007-05-29 5:56 ` Roland McGrath
2007-05-30 0:33 ` Albert Cahalan
2007-05-30 1:43 ` Eric W. Biederman
2007-07-26 7:34 ` Jan Engelhardt
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=m11wit34fo.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=davidel@xmailserver.org \
--cc=holt@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox