[lkml]   [2016]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/5 RFC] Add an interface to discover relationships between namespaces

I forgot to add --cc-cover for git send-email, so everyone who is in
Cc got only a cover letter. All messages were sent in mail lists.

Sorry for inconvenience.

On Thu, Jul 14, 2016 at 11:20 AM, Andrey Vagin <> wrote:
> Each namespace has an owning user namespace and now there is not way
> to discover these relationships.
> Pid and user namepaces are hierarchical. There is no way to discover
> parent-child relationships too.
> Why we may want to know relationships between namespaces?
> One use would be visualization, in order to understand the running system.
> Another would be to answer the question: what capability does process X have to
> perform operations on a resource governed by namespace Y?
> One more use-case (which usually called abnormal) is checkpoint/restart.
> In CRIU we age going to dump and restore nested namespaces.
> There [1] was a discussion about which interface to choose to determing
> relationships between namespaces.
> Eric suggested to add two ioctl-s [2]:
>> Grumble, Grumble. I think this may actually a case for creating ioctls
>> for these two cases. Now that random nsfs file descriptors are bind
>> mountable the original reason for using proc files is not as pressing.
>> One ioctl for the user namespace that owns a file descriptor.
>> One ioctl for the parent namespace of a namespace file descriptor.
> Here is an implementaions of these ioctl-s.
> [1]
> [2]
> Cc: "Eric W. Biederman" <>
> Cc: James Bottomley <>
> Cc: "Michael Kerrisk (man-pages)" <>
> Cc: "W. Trevor King" <>
> Cc: Alexander Viro <>
> Cc: Serge Hallyn <>
> --
> 2.5.5

 \ /
  Last update: 2016-07-15 00:41    [W:0.301 / U:3.424 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site