From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vivek Goyal Subject: Re: [PATCH 2/2] net: Implement SO_PEERCGROUP Date: Thu, 13 Mar 2014 15:53:49 -0400 Message-ID: <20140313195349.GM18914@redhat.com> References: <5320CAEC.6030008@amacapital.net> <1394658983.32465.203.camel@willson.li.ssimo.org> <1394673476.32465.215.camel@willson.li.ssimo.org> <1394675038.32465.223.camel@willson.li.ssimo.org> <1394733077.32465.243.camel@willson.li.ssimo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Simo Sorce , "linux-kernel@vger.kernel.org" , cgroups@vger.kernel.org, Network Development , "David S. Miller" , Tejun Heo , jkaluza@redhat.com, lpoetter@redhat.com, kay@redhat.com To: Andy Lutomirski Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Mar 13, 2014 at 10:55:16AM -0700, Andy Lutomirski wrote: [..] > >> 2. Docker is a container system, so use the "container" (aka > >> namespace) APIs. There are probably several clever things that could > >> be done with /proc//ns. > > > > pid is racy, if it weren't I would simply go straight > > to /proc//cgroups ... > > How about: > > open("/proc/self/ns/ipc", O_RDONLY); > send the result over SCM_RIGHTS? As I don't know I will ask. So what will server now do with this file descriptor of client's ipc namespace. IOW, what information/identifier does it contain which can be used to map to pre-configrued per container/per namespace policies. Thanks Vivek