[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1aauqv1n7.fsf@fess.ebiederm.org>
Date: Tue, 02 Mar 2010 13:45:16 -0800
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Jan Engelhardt <jengelh@...ozas.de>
Cc: Pavel Emelyanov <xemul@...allels.com>,
Daniel Lezcano <daniel.lezcano@...e.fr>, hadi@...erus.ca,
Patrick McHardy <kaber@...sh.net>,
Linux Netdev List <netdev@...r.kernel.org>,
containers@...ts.linux-foundation.org,
Netfilter Development Mailinglist
<netfilter-devel@...r.kernel.org>,
Ben Greear <greearb@...delatech.com>,
Serge Hallyn <serue@...ibm.com>,
Matt Helsley <matthltc@...ibm.com>
Subject: Re: [RFC][PATCH] ns: Syscalls for better namespace sharing control.
Jan Engelhardt <jengelh@...ozas.de> writes:
> On Tuesday 2010-03-02 16:03, Pavel Emelyanov wrote:
>
>>> I agree with all the points you and Pavel you talked about but I don't
>>> feel comfortable to have the current process to switch the pid namespace
>>> because of the process tree hierarchy (what will be the parent of the
>>> process when you enter the pid namespace for example).
>>
>>The answer is - the one, that used to be. I see no problems with it.
>>Do you?
>
> But perhaps it could be named "namespacefd" instead of nsfd, to reduce
> potential clashes (because glibc will usually just use the same name
> when making the syscall available as a C function).
Maybe. namespacefd seems like a real mouthful. I agree nsfd might be
a bit non-obvious for a rarish syscall.
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