From: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: [Devel] [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3)
Date: Tue, 04 Sep 2007 12:06:18 -0700 [thread overview]
Message-ID: <1188932778.28903.361.camel@localhost> (raw)
In-Reply-To: <20070904125019.GA22410-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
On Tue, 2007-09-04 at 07:50 -0500, Serge E. Hallyn wrote:
> > What do you do if there are no processes in a particular container?
>
> The nsproxy will have been released so you couldn't enter it anyway.
Yeah, we'd need some kind of other object to keep the nsproxy around and
hold a reference to it.
But, it also begs other questions about how we define the namespace
boundaries vs. containers. What if we have a normal container with
chroot'd process inside of it? Two such processes will not share an
nsproxy because the chroot'd one has switched filesystem namespaces.
Who is to say that the "container" is represented by one process's
nsproxy more than another?
-- Dave
next prev parent reply other threads:[~2007-09-04 19:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 20:04 [RFC] [PATCH 0/2] namespace enter through hijack Serge E. Hallyn
[not found] ` <20070829200420.GA4870-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-08-29 20:04 ` [RFC] [PATCH 1/2] namespace enter: introduce do_fork_task() Serge E. Hallyn
2007-08-29 20:05 ` [RFC] [PATCH 2/2] namespace enter: introduce sys_hijack (v3) Serge E. Hallyn
[not found] ` <20070829200515.GC4870-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-03 8:02 ` [Devel] " Paul Menage
[not found] ` <6599ad830709030102w6b5084d4w4a8a9a654e421527-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-04 12:50 ` Serge E. Hallyn
[not found] ` <20070904125019.GA22410-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-04 19:06 ` Dave Hansen [this message]
2007-09-04 19:32 ` Serge E. Hallyn
[not found] ` <20070904193256.GA494-6s5zFf/epYLPQpwDFJZrxKsjOiXwFzmk@public.gmane.org>
2007-09-05 16:15 ` Paul Menage
[not found] ` <6599ad830709050915r5c4fb424ha2081c7d8596aac6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2007-09-10 19:17 ` Serge E. Hallyn
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=1188932778.28903.361.camel@localhost \
--to=haveblue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@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.