From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Lezcano Subject: Re: [ABI REVIEW][PATCH 0/8] Namespace file descriptors Date: Fri, 24 Sep 2010 15:49:48 +0200 Message-ID: <4C9CAC7C.2080900@free.fr> References: <4C9CA16F.3000505@mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C9CA16F.3000505@mit.edu> Sender: linux-kernel-owner@vger.kernel.org To: Andrew Lutomirski Cc: "Eric W. Biederman" , Sukadev Bhattiprolu , Pavel Emelyanov , Pavel Emelyanov , Ulrich Drepper , netdev@vger.kernel.org, Jonathan Corbet , linux-kernel@vger.kernel.org, Jan Engelhardt , linux-fsdevel@vger.kernel.org, netfilter-devel@vger.kernel.org, Michael Kerrisk , Linux Containers , Ben Greear , Linus Torvalds , David Miller , Al Viro List-Id: containers.vger.kernel.org On 09/24/2010 03:02 PM, Andrew Lutomirski wrote: > Eric W. Biederman wrote: >> Introduce file for manipulating namespaces and related syscalls. >> files: >> /proc/self/ns/ >> >> syscalls: >> int setns(unsigned long nstype, int fd); >> socketat(int nsfd, int family, int type, int protocol); >> > > How does security work? Are there different kinds of fd that give (say) pin-the-namespace permission, socketat permission, and setns permission? AFAICS, socketat, setns and "set netns by fd" only accept fd from /proc//ns/. setns does : file = proc_ns_fget(fd); if (IS_ERR(file)) return PTR_ERR(file); proc_ns_fget checks if (file->f_op != &ns_file_operations) socketat and get_net_ns_by_fd: net = get_net_ns_by_fd(fd); this one calls proc_ns_fget. We have the guarantee here, the fd is resulting from an open of the file with the right permissions. Another way to pin the namespace, would be to mount --bind /proc//ns/ but we have to be root to do that ...