linux-kernel - Re: [PATCH net-next] rxrpc: Support network namespacing

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: <20170525.132014.914695127659161968.davem@davemloft.net>
Date:   Thu, 25 May 2017 13:20:14 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     dhowells@...hat.com
Cc:     netdev@...r.kernel.org, linux-afs@...ts.infradead.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next] rxrpc: Support network namespacing

From: David Howells <dhowells@...hat.com>
Date: Wed, 24 May 2017 17:02:32 +0100

> Support network namespacing in AF_RXRPC with the following changes:
> 
>  (1) All the local endpoint, peer and call lists, locks, counters, etc. are
>      moved into the per-namespace record.
> 
>  (2) All the connection tracking is moved into the per-namespace record
>      with the exception of the client connection ID tree, which is kept
>      global so that connection IDs are kept unique per-machine.
> 
>  (3) Each namespace gets its own epoch.  This allows each network namespace
>      to pretend to be a separate client machine.
> 
>  (4) The /proc/net/rxrpc_xxx files are now called /proc/net/rxrpc/xxx and
>      the contents reflect the namespace.
> 
> fs/afs/ should be okay with this patch as it explicitly requires the current
> net namespace to be init_net to permit a mount to proceed at the moment.  It
> will, however, need updating so that cells, IP addresses and DNS records are
> per-namespace also.
> 
> Signed-off-by: David Howells <dhowells@...hat.com>

Applied.