Skip to content

RFC Remove NETIF_F_NETNS_LOCAL from software devices.

Rami Rosen netdev 2 versions – In review

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 RFC Latest2 patches 3 repliesIn review
  2. v1 RFC3 patches 1 replySuperseded

Patches in v2 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/2ppp: remove NETIF_F_NETNS_LOCAL from ppp device features.drivers/net/ppp/ppp_generic.c+0 -11 reply
2/2bridge: remove NETIF_F_NETNS_LOCAL from bridge device features.net/bridge/br_device.c+1 -11 reply

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [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(-)
Signature · 1 line
1.7.11.7

Read the cover letter in its thread