[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160709031528.GA25507@odin.tremily.us>
Date: Fri, 8 Jul 2016 20:15:28 -0700
From: "W. Trevor King" <wking@...mily.us>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: "Serge E. Hallyn" <serge@...lyn.com>,
"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
Linux API <linux-api@...r.kernel.org>,
Containers <containers@...ts.linux-foundation.org>,
lkml <linux-kernel@...r.kernel.org>,
Andy Lutomirski <luto@...capital.net>, criu@...nvz.org,
"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: Introspecting userns relationships to other namespaces?
On Thu, Jul 07, 2016 at 08:01:52AM -0700, James Bottomley wrote:
> In theory, we could get nsfs to show this information as an option
> (just add a show_options entry to the superblock ops), but the
> problem is that although each namespace has a parent user_ns,
> there's no way to get it without digging in the namespace specific
> structure. Probably we should restructure to move it into
> ns_common, then we could display it (and enforce all namespaces
> having owning user_ns) but it would be a reasonably large (but
> mechanical) change.
It sounds like everyone is either positive or or neutral on this
groundwork, even if we haven't decided if/how to expose the
information to userspace. I'm happy to work up a patch while the rest
of the discussion continues. I'm also happy to let someone else work
up the patch, if anyone else is chomping at the bit ;).
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
Download attachment "signature.asc" of type "application/pgp-signature" (820 bytes)
Powered by blists - more mailing lists