From: Cedric Le Goater <clg-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Linux Containers
<containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>,
Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
Subject: Re: Q: How complete is the pid namespace in mainline
Date: Fri, 26 Oct 2007 10:52:38 +0200 [thread overview]
Message-ID: <4721AAD6.60501@fr.ibm.com> (raw)
In-Reply-To: <m1bqam4fpg.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
Eric W. Biederman wrote:
> Guys how complete do you fee the pid namespace support is that
> has been merged into Linus's tree?
>
> My impression until I started reading through code earlier today
> was that the support was just about done except for a couple of
> tricky details.
Yes It looks sane.
Here's what I have in mind :
* there are some patches from suka that make sure the pid namespace init
is not getting abusively killed by one of this children
* the pid cleanup is not complete
. locks
. kthread (i should work soon on improving kthread to support
signals)
IMO, the proc mount shouldn't be under the pid namespace. we will
need that sooner or later.
C.
next prev parent reply other threads:[~2007-10-26 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 5:17 Q: How complete is the pid namespace in mainline Eric W. Biederman
[not found] ` <m1bqam4fpg.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-10-26 8:52 ` Cedric Le Goater [this message]
[not found] ` <4721AAD6.60501-NmTC/0ZBporQT0dZR+AlfA@public.gmane.org>
2007-10-26 9:33 ` Eric W. Biederman
2007-10-26 17:17 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
[not found] ` <20071026171718.GB11942-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-26 18:17 ` Eric W. Biederman
[not found] ` <m1r6jh211e.fsf-T1Yj925okcoyDheHMi7gv2pdwda3JcWeAL8bYrjMMd8@public.gmane.org>
2007-10-26 21:29 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
[not found] ` <20071026212959.GA15511-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-10-26 23:09 ` 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=4721AAD6.60501@fr.ibm.com \
--to=clg-nmtc/0zbporqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.