From: ebiederm@xmission.com (Eric W. Biederman)
To: Andrew Morton <akpm@osdl.org>
Cc: arjan@infradead.org, linux-kernel@vger.kernel.org,
B.Steinbrink@gmx.de, viro@ftp.linux.org.uk
Subject: Re: + daemonize-detach-from-current-namespace.patch added to -mm tree
Date: Mon, 20 Feb 2006 11:11:13 -0700 [thread overview]
Message-ID: <m13bidnbni.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20060220020943.1d9eac25.akpm@osdl.org> (Andrew Morton's message of "Mon, 20 Feb 2006 02:09:43 -0800")
Andrew Morton <akpm@osdl.org> writes:
> ebiederm@xmission.com (Eric W. Biederman) wrote:
>>
>> I am beginning to suspect that we will want to fix kernel_thread so it
>> creates copies of the init_task rather than copies of whatever random
>> user space process we happen to be a member of at the time. With an
>> enhanced kernel_thread this problem could more easily avoided, as
>> we add additional namespaces to the kernel.
>
> You wouldn't believe the problems we had with kernel_thread followed by
> call_usermodehelper() due to inheritance of random stuff from the userspace
> parent.
>
> A suitable solution is to stop using kernel_thread(), migrate to the
> kthread API - that way the threads are parented by keventd which is a known
> and good environment.
Thanks. This sounds worth investigating.
On the other hand call_usermodehelper is the one case where we might
want to share some of the attributes with an existing process, at
least if we ever want it to run in a non-default namespace.
Eric
next prev parent reply other threads:[~2006-02-20 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200602200438.k1K4ct5n013388@shell0.pdx.osdl.net>
2006-02-20 8:46 ` Arjan van de Ven
2006-02-20 9:04 ` Eric W. Biederman
2006-02-20 10:09 ` Andrew Morton
2006-02-20 18:11 ` Eric W. Biederman [this message]
2006-02-21 0:30 ` 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=m13bidnbni.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=B.Steinbrink@gmx.de \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ftp.linux.org.uk \
/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®