From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: unshare() pid ns
Date: Thu, 30 Aug 2007 18:11:27 +0400 [thread overview]
Message-ID: <46D6D00F.7090303@openvz.org> (raw)
In-Reply-To: <20070830133422.GA28129-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
Serge E. Hallyn wrote:
> Quoting Pavel Emelyanov (xemul-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org):
>> sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org wrote:
>>> Pavel,
>>> unshare() of pid ns seems to fail with -EINVAL in 2.6.23-rc3-mm1.
>>> I thought we supported it in the earlier patchsets. I guess
>>> I missed that in the review of recent patchsets.
>> I disabled unsharing of pid namespaces because it's almost
>> impossible. Look - you have to reattach all the pids to the
>> task with saving its ids as seen in previous namespaces.
>
> We agree, but thought you for some perverse reason preferred unshare to
> clone for pidns :)
I did that in my first version of patches, but then realized
that such problem (the need in reattaching pids) makes the
unsharing ugly.
BTW, unsharing of a pid namespace is a valid operation, so I
think I will enable it in the nearest future. I have some
thought on how to make such a reattach ;)
> Thanks for clarifying.
>
> -serge
>
next prev parent reply other threads:[~2007-08-30 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 5:29 unshare() pid ns sukadev-r/Jw6+rmf7HQT0dZR+AlfA
[not found] ` <20070830052928.GA27864-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-08-30 8:10 ` Pavel Emelyanov
[not found] ` <46D67B8B.2000606-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-08-30 13:34 ` Serge E. Hallyn
[not found] ` <20070830133422.GA28129-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-08-30 14:11 ` Pavel Emelyanov [this message]
[not found] ` <46D6D00F.7090303-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2007-08-30 14:35 ` Serge E. Hallyn
2007-08-30 16:34 ` Cedric Le Goater
2007-08-30 14:19 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
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=46D6D00F.7090303@openvz.org \
--to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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.