mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "W. Trevor King" <wking@tremily.us>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Andrew Vagin <avagin@virtuozzo.com>,
	criu@openvz.org, Linux API <linux-api@vger.kernel.org>,
	Containers <containers@lists.linux-foundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	mtk.manpages@gmail.com
Subject: Re: Introspecting userns relationships to other namespaces?
Date: Thu, 7 Jul 2016 23:16:36 -0700	[thread overview]
Message-ID: <20160708061636.GA5528@odin.tremily.us> (raw)
In-Reply-To: <20160708052650.GM4916@odin.tremily.us>

[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]

On Thu, Jul 07, 2016 at 10:26:50PM -0700, W. Trevor King wrote:
> And if you want to put that whole ancestor tree in fdinfo, you have
> to come up with some way to handle the two-parent branching.

Going towards the roots is nice, because you know a given namespace
will only have two parents, but it leaks information about the system
into the container.  It's probably better to follow the NStgid,
etc. example and only walk toward the leaves.  So a (privileged?)
process in the root namespace could see the whole tree, while a
process in non-root namespaces could only see their namespaces and
descendants.  In situations where you were part of a namespace that
belonged to an external user namespace (e.g. you nsenter a child user
namespace but are still in the root PID namespace), you'd want an
“unknown” entry for the parent you couldn't see.

Cheers,
Trevor

-- 
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-07-08  6:16 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <c2a26220-69f2-f2f5-491a-e43abd9a6f92@gmail.com>
     [not found] ` <87r3b7pxja.fsf@x220.int.ebiederm.org>
2016-07-06  8:41   ` Michael Kerrisk (man-pages)
2016-07-06 14:13     ` Serge E. Hallyn
2016-07-06 15:46       ` Eric W. Biederman
2016-07-08  1:57         ` [CRIU] " Andrew Vagin
2016-07-08  7:44           ` Eric W. Biederman
2016-07-08 14:35             ` James Bottomley
2016-07-08 20:38               ` Andrew Vagin
2016-07-08 20:50                 ` W. Trevor King
2016-07-08 22:19                 ` James Bottomley
2016-07-08 22:19                 ` James Bottomley
2016-07-08 23:52                   ` Eric W. Biederman
2016-07-09  0:15                     ` James Bottomley
2016-07-09  3:05                       ` Eric W. Biederman
2016-07-09  7:26                         ` Andrew Vagin
2016-07-09 10:31                           ` James Bottomley
2016-07-09 10:32                           ` James Bottomley
2016-07-09 18:15                           ` Eric W. Biederman
2016-07-09 18:29                             ` Eric W. Biederman
2016-07-13  0:08                               ` Andrew Vagin
2016-07-13  3:59                                 ` W. Trevor King
2016-07-07  8:15       ` Michael Kerrisk (man-pages)
2016-07-07 13:36         ` Serge E. Hallyn
2016-07-07 15:01           ` James Bottomley
2016-07-07 18:21             ` Michael Kerrisk (man-pages)
2016-07-07 18:24               ` Serge E. Hallyn
2016-07-07 19:17               ` James Bottomley
2016-07-08  2:16                 ` [CRIU] " Andrew Vagin
2016-07-08  3:00                   ` Andrew Vagin
2016-07-08  3:26                     ` James Bottomley
2016-07-08  5:26                       ` W. Trevor King
2016-07-08  6:16                         ` W. Trevor King [this message]
2016-07-08  6:54                         ` Andrew Vagin
2016-07-08  7:18                           ` W. Trevor King
2016-07-08  5:41                       ` [CRIU] " Andrei Vagin
2016-07-08  5:47                         ` Andrei Vagin
2016-07-08  6:07                         ` James Bottomley
2016-07-08 11:17                       ` Michael Kerrisk (man-pages)
2016-07-08  3:20                   ` James Bottomley
2016-07-08  6:09                     ` Andrew Vagin
2016-07-08 11:11                 ` Michael Kerrisk (man-pages)
2016-07-09  3:15             ` W. Trevor King
2016-07-09  3:13               ` Eric W. Biederman
2016-07-10  5:36                 ` [CRIU] " Andrew Vagin
2016-07-10 20:29                   ` Eric W. Biederman
2016-07-10 21:06                     ` James Bottomley
2016-07-11 20:55                       ` Andrew Vagin

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=20160708061636.GA5528@odin.tremily.us \
    --to=wking@tremily.us \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=avagin@virtuozzo.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=criu@openvz.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.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

all inboxes | Powered by JetHome®