linux-kernel - Re: [PATCH 5/5] net: namespace: allow setting NSIDs outside current namespace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <739c409a-bfbf-99c0-9624-38264d52087a@6wind.com>
Date:   Tue, 5 Nov 2019 16:49:32 +0100
From:   Nicolas Dichtel <nicolas.dichtel@...nd.com>
To:     Jonas Bonn <jonas@...rbonn.se>, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     davem@...emloft.net
Subject: Re: [PATCH 5/5] net: namespace: allow setting NSIDs outside current
 namespace

Le 05/11/2019 à 09:11, Jonas Bonn a écrit :
> Currently it is only possible to move an interface to a new namespace if
> the destination namespace has an ID in the interface's current namespace.
> If the interface already resides outside of the current namespace, then
> we may need to assign the destination namespace an ID in the interface's
> namespace in order to effect the move.
> 
> This patch allows namespace ID's to be created outside of the current
> namespace.  With this, the following is possible:
> 
> i)    Our namespace is 'A'.
> ii)   The interface resides in namespace 'B'
> iii)  We can assign an ID for NS 'A' in NS 'B'
> iv)   We can then move the interface into our own namespace.
> 
> and
> 
> i)   Our namespace is 'A'; namespaces 'B' and 'C' also exist
> ii)  We can assign an ID for namespace 'C' in namespace 'B'
> iii) We can then create a VETH interface directly in namespace 'B' with
> the other end in 'C', all without ever leaving namespace 'A'
> 
> Signed-off-by: Jonas Bonn <jonas@...rbonn.se>
Acked-by: Nicolas Dichtel <nicolas.dichtel@...nd.com>