netdev - Re: [PATCH net-next] can: initial support for network namespaces

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 for Android: free password hash cracker in your pocket

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

Message-ID: <57d4cb90-b96e-27a4-3ac5-66ebb8f1e8f4@hartkopp.net>
Date:   Thu, 16 Feb 2017 14:47:39 +0100
From:   Oliver Hartkopp <socketcan@...tkopp.net>
To:     Mario Kicherer <dev@...herer.org>
Cc:     netdev@...r.kernel.org,
        "linux-can@...r.kernel.org" <linux-can@...r.kernel.org>
Subject: Re: [PATCH net-next] can: initial support for network namespaces

Hello Mario,

thanks for your patch.

On 02/16/2017 12:39 PM, Mario Kicherer wrote:
> This patch adds initial support for network namespaces. The changes only
> enable support in the CAN raw, proc and af_can code. GW and BCM still
> have their checks that ensure that they are used only from the main
> namespace.
>
> The patch boils down to moving the global structures, i.e. the global
> filter list and their /proc stats, into a per-namespace structure and passing
> around the corresponding "struct net" in a lot of different places.
>
> Signed-off-by: Mario Kicherer <dev@...herer.org>

Although it does not apply on the latest kernel due to this patch:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=f1712c73714088a7252d276a57126d56c7d37e64

Please rebase your patch to the latest kernel tree and post it again.

Additionally you should post CAN related stuff to the linux-can ML (see 
CC) and the CAN maintainers found in the MAINTAINERS file. In this case 
cross posting to netdev ML is fine as namespaces are very netdev related.

Do you have an idea how to go with namespace aware virtual CAN 
interfaces to link the namespaces?

Regards,
Oliver