[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <m1ei2o5ljy.fsf@fess.ebiederm.org>
Date: Mon, 20 Jun 2011 12:50:57 -0700
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serge@...lyn.com>
Cc: Linux Containers <containers@...ts.osdl.org>,
Alexey Dobriyan <adobriyan@...il.com>, netdev@...r.kernel.org,
David Lamparter <equinox@...c24.net>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] proc: Usable inode numbers for the namespace file descriptors.
"Serge E. Hallyn" <serge@...lyn.com> writes:
> Quoting Eric W. Biederman (ebiederm@...ssion.com):
>>
>> Assign a unique proc inode to each namespace, yielding an
>> identifier that userspace can use for identifying a namespace.
>>
>> This has been a long requested feature and only blocked because
>> a naive implementation would put the id in a global space and
>> would ultimately require having a namespace for the names of
>> namespaces, making migration and certain virtualization tricks
>> impossible.
>>
>> We still don't have per superblock inode numbers for proc, which
>> appears necessary for application unaware checkpoint/restart and
>> migrations (if the application is using namespace filedescriptors)
>> but that is now allowd by the design if it becomes important.
>>
>> I have preallocated the ipc and uts initial proc inode numbers so
>> their structures can be statically initialized.
>>
>> Signed-off-by: Eric W. Biederman <ebiederm@...ssion.com>
>
> I've not looked at the setns patches enough, but from what I can see
> here it looks good.
>
> Acked-by: Serge Hallyn <serge@...lyn.com>
Thanks.
There are bugs in my existing proc bits that I am working on fixing so
this second patch will have a small update, before it gets merged.
But posting the patches I was looking for a little review and I was
announcing I had solved the technical problem of how we talk about
namespaces, without needing to introduce another namespace for
namespaces.
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists