netdev - [RFC PATCH v2 net-next 0/2] Remove NETIF_F_NETNS

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-next>] [day] [month] [year] [list]

Message-Id: <1357543176-15352-1-git-send-email-ramirose@gmail.com>
Date:	Mon,  7 Jan 2013 09:19:34 +0200
From:	Rami Rosen <ramirose@...il.com>
To:	davem@...emloft.net
Cc:	netdev@...r.kernel.org, shemminger@...tta.com,
	ebiederm@...ssion.com, Rami Rosen <ramirose@...il.com>
Subject: [RFC PATCH v2 net-next 0/2] Remove NETIF_F_NETNS_LOCAL from software devices.

When NETIF_F_NETNS_LOCAL feature is set in some network device,  
we do not allow this device to be moved from one network namespace 
to another (see dev_change_net_namespace()). Vlan device is not considered 
a local device and does not have the NETIF_F_NETNS_LOCAL feature. There is no 
reason that software devices like ppp and bridge will set the
NETIF_F_NETNS_LOCAL feature. This patchset removes NETIF_F_NETNS_LOCAL
from ppp and bridge devices.

* Changes from v1
	Do not remove NETIF_F_NETNS_LOCAL from vxlan devices. Moving vxlan device 
	to a different namesapce does not move the state of the UDP socket related 
	to this vxlan device (Following Stephen Hemminger comment).
	
Rami Rosen (2):
  [RFC PATCH v2 net-next 1/3] ppp: remove NETIF_F_NETNS_LOCAL from ppp
    device features.
  [RFC PATCH v2 net-next 2/3] bridge: remove NETIF_F_NETNS_LOCAL from
    bridge device features.

 drivers/net/ppp/ppp_generic.c | 1 -
 net/bridge/br_device.c        | 2 +-
 2 files changed, 1 insertion(+), 2 deletions(-)

-- 
1.7.11.7

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html