From: ebiederm@xmission.com (Eric W. Biederman)
To: Oleg Nesterov <oleg@tv-sign.ru>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pavel Emelyanov <xemul@openvz.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH? 3/3] move daemonized kernel threads into the swapper's session
Date: Mon, 26 Nov 2007 11:57:36 -0700 [thread overview]
Message-ID: <m14pf8omvz.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20071126142556.GA16531@tv-sign.ru> (Oleg Nesterov's message of "Mon, 26 Nov 2007 17:25:56 +0300")
Oleg Nesterov <oleg@tv-sign.ru> writes:
> Any reason why daemonized kthread still uses 1,1 special pids? This patch
> sets 0,0 pids, this matches kthread_create'ed threads.
You got it in your reply...
> Signed-off-by: Oleg Nesterov <oleg@tv-sign.ru>
Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>
Hmm. I wonder if we could ensure kernel_thread always
returns a global pid_t, and then reallocate the struct
pid for the task we have just daemonized so that it only
has a single pid in the init_pid_ns.
That would remove our capturing of child pid namespaces.
Eric
next prev parent reply other threads:[~2007-11-26 18:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-26 14:25 Oleg Nesterov
2007-11-26 18:20 ` Oleg Nesterov
2007-11-26 18:57 ` Eric W. Biederman [this message]
2007-11-26 19:23 ` 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=m14pf8omvz.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=xemul@openvz.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
all inboxes | Powered by JetHome®