From: Richard Weinberger <richard@nod.at>
To: Pavel Emelyanov <xemul@parallels.com>
Cc: Vasily Kulikov <segoon@openwall.com>,
containers@lists.linux-foundation.org,
Serge Hallyn <serge.hallyn@ubuntu.com>,
linux-kernel@vger.kernel.org, Oleg Nesterov <oleg@redhat.com>,
David Howells <dhowells@redhat.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH v2] /proc/pid/status: show all sets of pid according to ns
Date: Thu, 29 May 2014 12:19:17 +0200 [thread overview]
Message-ID: <538709A5.60000@nod.at> (raw)
In-Reply-To: <5387059E.9010105@parallels.com>
Am 29.05.2014 12:02, schrieb Pavel Emelyanov:
>>> We need to know what pid namespaces a task lives in and how pid, sid and
>>> pgid look in all of them. A short example with pids only
>>
>> So use case is to checkpoint/restore nested containers? :)
>
> Yes, but there's one more scenario. AFAIK some applications create pid namespaces
> themselves, without starting what is typically called "a container" :) And when
> such an applications are run inside, well ... "more real" container (e.g. using
> openvz, lxc or docker tools) we face this issue.
Do you know such an application?
I'm a aware of systemd which uses CLONE_NEWNET/NS to implement security features.
We could add a directory like /proc/<pidX>/ns/proc/ which would contain everything
from /proc/<pidX inside the namespace>/.
This needs definitely more discussion and must not solved by ad-hoc solutions.
Thanks,
//richard
next prev parent reply other threads:[~2014-05-29 10:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-28 10:24 [PATCH v2] /proc/pid/status: show all sets of pid according to ns Chen Hanxiao
2014-05-28 12:44 ` Pavel Emelyanov
2014-05-28 18:28 ` Vasily Kulikov
2014-05-28 19:27 ` Pavel Emelyanov
2014-05-29 5:59 ` Vasily Kulikov
2014-05-29 9:07 ` Pavel Emelyanov
2014-05-29 9:21 ` Richard Weinberger
2014-05-29 9:41 ` Pavel Emelyanov
2014-05-29 9:54 ` Richard Weinberger
2014-05-29 10:02 ` Pavel Emelyanov
2014-05-29 10:19 ` Richard Weinberger [this message]
2014-05-29 10:36 ` Pavel Emelyanov
2014-05-29 9:53 ` chenhanxiao
2014-05-29 10:40 ` Pavel Emelyanov
2014-05-29 11:12 ` Vasily Kulikov
2014-05-29 11:31 ` Pavel Emelyanov
2014-05-29 11:59 ` Vasily Kulikov
2014-05-29 12:53 ` Pavel Emelyanov
2014-05-31 6:07 ` Vasily Kulikov
2014-05-31 20:08 ` 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=538709A5.60000@nod.at \
--to=richard@nod.at \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=segoon@openwall.com \
--cc=serge.hallyn@ubuntu.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/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