public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Serge E. Hallyn" <serge@hallyn.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: "Chen, Hanxiao" <chenhanxiao@cn.fujitsu.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"containers@lists.linux-foundation.org" 
	<containers@lists.linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	Serge Hallyn <serge.hallyn@ubuntu.com>,
	Mateusz Guzik <mguzik@redhat.com>,
	David Howells <dhowells@redhat.com>,
	"Pavel Emelyanov (xemul@parallels.com)" <xemul@parallels.com>
Subject: Re: [PATCHv3 2/2] /proc/PID/status: show all sets of pid according to ns
Date: Tue, 30 Sep 2014 18:07:55 +0200	[thread overview]
Message-ID: <20140930160755.GB6838@mail.hallyn.com> (raw)
In-Reply-To: <20140930160549.GA6838@mail.hallyn.com>

Quoting Serge E. Hallyn (serge@hallyn.com):
> Quoting Chen, Hanxiao (chenhanxiao@cn.fujitsu.com):
> > Hi,
> > 
> > > -----Original Message-----
> > > From: Serge E. Hallyn [mailto:serge@hallyn.com]
> > > Sent: Monday, September 29, 2014 10:00 PM
> > > Subject: Re: [PATCHv3 2/2] /proc/PID/status: show all sets of pid according to
> > > ns
> > [snip]
> > > > >
> > > > > This patch adds four fields: NStgid, NSpid, NSpgid and NSsid:
> > > > > a) In init_pid_ns, nothing changed;
> > > > >
> > > > > b) In one pidns, will tell the pid inside containers:
> > > > > NStgid:	21776   5       1
> > > > > NSpid:  21776   5       1
> > > > > NSpgid:	21776   5       1
> > > > > NSsid:  21729   1       0
> > > > > ** Process id is 21776 in level 0, 5 in level 1, 1 in level 2.
> > > > >
> > > > > c) If pidns is nested, it depends on which pidns are you in.
> > > > > NStgid: 5       1
> > > > > NSpid:  5       1
> > > > > NSpgid: 5       1
> > > > > NSsid:  1       0
> > > > > ** Views from level 1
> > > > >
> > > >
> > > > This patch is simple, useful and safe.
> > > > But currently there is not any feedbacks.
> > > >
> > > > Any comments or ideas?
> > > 
> > > Thanks, Chen.  The code looks fine.  My concern is that you are
> > > exposing information which cannot be checkpointed and restarted.
> > > In particular, if I'm inside a nested container, so I'm in pidns
> > > level 3, then my own NSpid info, when I read it, will show the
> > > pids at parent namespaces.  If I'm restarted at the third pidns
> > > level, only the one pid can be restored.
> > 
> > If you're in level 3, read your own proc, only level 3's NSpid info
> > will be shown. No parent namesapces info could be seen.
> 
> D'oh!  Sorry, I see, you're starting at ns->level.  And ns is the ns
> of the proc mount, not the caller.  that looks good.
> 
> So
> 
> Acked-by: Serge Hallyn <serge.hallyn@canonical.com>

Also

Tested-by: Serge Hallyn <serge.hallyn@canonical.com>

as I've tested this between a few containers.

      reply	other threads:[~2014-09-30 16:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-24 10:00 [PATCHv3 0/2] ns, procfs: pid conversion between ns and showing pidns hierarchy Chen Hanxiao
2014-09-24 10:00 ` [PATCHv3 1/2] procfs: show hierarchy of pid namespace Chen Hanxiao
2014-09-24 17:45   ` Mateusz Guzik
2014-09-25  9:45     ` Chen, Hanxiao
2014-09-24 10:00 ` [PATCHv3 2/2] /proc/PID/status: show all sets of pid according to ns Chen Hanxiao
2014-09-25 12:52   ` Chen, Hanxiao
2014-09-26 10:20   ` Chen, Hanxiao
2014-09-29 14:00     ` Serge E. Hallyn
2014-09-30 10:37       ` Chen, Hanxiao
2014-09-30 16:05         ` Serge E. Hallyn
2014-09-30 16:07           ` Serge E. Hallyn [this message]

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=20140930160755.GB6838@mail.hallyn.com \
    --to=serge@hallyn.com \
    --cc=chenhanxiao@cn.fujitsu.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mguzik@redhat.com \
    --cc=oleg@redhat.com \
    --cc=richard.weinberger@gmail.com \
    --cc=serge.hallyn@ubuntu.com \
    --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