From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Dichtel Subject: Re: [RFC PATCH net-next v2 0/5] netns: allow to identify peer netns Date: Wed, 24 Sep 2014 11:31:55 +0200 Message-ID: <54228F8B.2030804@6wind.com> References: <1411478430-4989-1-git-send-email-nicolas.dichtel@6wind.com> Reply-To: nicolas.dichtel-pdR9zngts4EAvxtiuMwx3w@public.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8"; Format="flowed" Content-Transfer-Encoding: base64 Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: Andy Lutomirski Cc: Network Development , Linux Containers , "linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org" , Stephen Hemminger , "Eric W. Biederman" , Linux API , Andrew Morton , "David S. Miller" List-Id: containers.vger.kernel.org TGUgMjMvMDkvMjAxNCAyMToyNiwgQW5keSBMdXRvbWlyc2tpIGEgw6ljcml0IDoKPiBPbiBUdWUs IFNlcCAyMywgMjAxNCBhdCA2OjIwIEFNLCBOaWNvbGFzIERpY2h0ZWwKPiA8bmljb2xhcy5kaWNo dGVsQDZ3aW5kLmNvbT4gd3JvdGU6Cj4+IFRoZSBnb2FsIG9mIHRoaXMgc2VyaWUgaXMgdG8gYmUg YWJsZSB0byBtdWx0aWNhc3QgbmV0bGluayBtZXNzYWdlcyB3aXRoIGFuCj4+IGF0dHJpYnV0ZSB0 aGF0IGlkZW50aWZ5IGEgcGVlciBuZXRucy4KPj4gVGhpcyBpcyBuZWVkZWQgYnkgdGhlIHVzZXJs YW5kIHRvIGludGVycHJldCBzb21lIGluZm9ybWF0aW9ucyBjb250YWluZWQgaW4KPj4gbmV0bGlu ayBtZXNzYWdlcyAobGlrZSBJRkxBX0xJTksgdmFsdWUsIGJ1dCBhbHNvIHNvbWUgb3RoZXIgYXR0 cmlidXRlcyBpbiBjYXNlCj4+IG9mIHgtbmV0bnMgbmV0ZGV2aWNlIChzZWUgYWxzbwo+PiBodHRw Oi8vdGhyZWFkLmdtYW5lLm9yZy9nbWFuZS5saW51eC5uZXR3b3JrLzMxNTkzMy9mb2N1cz0zMTYw NjQgYW5kCj4+IGh0dHA6Ly90aHJlYWQuZ21hbmUub3JnL2dtYW5lLmxpbnV4Lmtlcm5lbC5jb250 YWluZXJzLzI4MzAxL2ZvY3VzPTQyMzkpKS4KPj4KPj4gSWRzIGFyZSBzdG9yZWQgaW4gdGhlIHBh cmVudCB1c2VyIG5hbWVzcGFjZS4gVGhlc2UgaWRzIGFyZSB2YWxpZCBvbmx5IGluc2lkZQo+PiB0 aGlzIHVzZXIgbmFtZXNwYWNlLiBUaGUgdXNlciBjYW4gcmV0cmlldmUgdGhlc2UgaWRzIHZpYSBh IG5ldyBuZXRsaW5rIG1lc3NhZ2VzLAo+PiBidXQgb25seSBpZiBwZWVyIG5ldG5zIGFyZSBpbiB0 aGUgc2FtZSB1c2VyIG5hbWVzcGFjZS4KPgo+IFdoYXQgYWJvdXQgdGhlIHBhcmVudCAvIGFuY2Vz dG9ycyBvZiB0aGUgb3duaW5nIHVzZXJucz8gIENhbiBwcm9jZXNzZXMKPiBpbiB0aG9zZSB1c2Vy bnNlcyBzZWUgYW55IGZvcm0gb2YgbmV0bnMgaWQ/CldpdGggdGhpcyBzZXJpZSBuby4gSSdtIG5v dCBzdXJlIGlmIGFuY2VzdG9ycyByZWFsbHkgbmVlZHMgdG8gYmUgYWJsZSB0bwpnZXQgdGhlc2Ug aWRzLiBXaGF0IGlzIHlvdXIgb3Bpbmlvbj8KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX18KQ29udGFpbmVycyBtYWlsaW5nIGxpc3QKQ29udGFpbmVyc0BsaXN0 cy5saW51eC1mb3VuZGF0aW9uLm9yZwpodHRwczovL2xpc3RzLmxpbnV4Zm91bmRhdGlvbi5vcmcv bWFpbG1hbi9saXN0aW5mby9jb250YWluZXJz From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753238AbaIXJcg (ORCPT ); Wed, 24 Sep 2014 05:32:36 -0400 Received: from mail-wg0-f52.google.com ([74.125.82.52]:61268 "EHLO mail-wg0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751603AbaIXJb6 (ORCPT ); Wed, 24 Sep 2014 05:31:58 -0400 Message-ID: <54228F8B.2030804@6wind.com> Date: Wed, 24 Sep 2014 11:31:55 +0200 From: Nicolas Dichtel Reply-To: nicolas.dichtel@6wind.com Organization: 6WIND User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1 MIME-Version: 1.0 To: Andy Lutomirski CC: Network Development , Linux Containers , "linux-kernel@vger.kernel.org" , Linux API , "David S. Miller" , "Eric W. Biederman" , Stephen Hemminger , Andrew Morton Subject: Re: [RFC PATCH net-next v2 0/5] netns: allow to identify peer netns References: <1411478430-4989-1-git-send-email-nicolas.dichtel@6wind.com> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Le 23/09/2014 21:26, Andy Lutomirski a écrit : > On Tue, Sep 23, 2014 at 6:20 AM, Nicolas Dichtel > wrote: >> The goal of this serie is to be able to multicast netlink messages with an >> attribute that identify a peer netns. >> This is needed by the userland to interpret some informations contained in >> netlink messages (like IFLA_LINK value, but also some other attributes in case >> of x-netns netdevice (see also >> http://thread.gmane.org/gmane.linux.network/315933/focus=316064 and >> http://thread.gmane.org/gmane.linux.kernel.containers/28301/focus=4239)). >> >> Ids are stored in the parent user namespace. These ids are valid only inside >> this user namespace. The user can retrieve these ids via a new netlink messages, >> but only if peer netns are in the same user namespace. > > What about the parent / ancestors of the owning userns? Can processes > in those usernses see any form of netns id? With this serie no. I'm not sure if ancestors really needs to be able to get these ids. What is your opinion?