From: Rami Rosen <ramirose@gmail•com>
To: davem@davemloft•net
Cc: netdev@vger•kernel.org, shemminger@vyatta•com,
ebiederm@xmission•com, Rami Rosen <ramirose@gmail•com>
Subject: [RFC PATCH v2 net-next 0/2] Remove NETIF_F_NETNS_LOCAL from software devices.
Date: Mon, 7 Jan 2013 09:19:34 +0200 [thread overview]
Message-ID: <1357543176-15352-1-git-send-email-ramirose@gmail.com> (raw)
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
next reply other threads:[~2013-01-07 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 7:19 Rami Rosen [this message]
2013-01-07 7:19 ` [RFC PATCH v2 net-next 1/2] ppp: remove NETIF_F_NETNS_LOCAL from ppp device features Rami Rosen
2013-01-07 9:16 ` Eric W. Biederman
2013-01-07 7:19 ` [RFC PATCH v2 net-next 2/2] bridge: remove NETIF_F_NETNS_LOCAL from bridge " Rami Rosen
2013-01-07 9:20 ` Eric W. Biederman
2013-01-07 9:25 ` [RFC PATCH v2 net-next 0/2] Remove NETIF_F_NETNS_LOCAL from software devices Eric W. Biederman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1357543176-15352-1-git-send-email-ramirose@gmail.com \
--to=ramirose@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=ebiederm@xmission$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=shemminger@vyatta$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox