All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, ebiederm@xmission.com,
	shemminger@vyatta.com, Rami Rosen <ramirose@gmail.com>
Subject: [RFC PATCH net-next 0/3] Remove NETIF_F_NETNS_LOCAL from software devices.
Date: Thu,  3 Jan 2013 11:25:18 +0200	[thread overview]
Message-ID: <1357205121-4700-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 vxlan, ppp and bridge, will set the
NETIF_F_NETNS_LOCAL feature. This patchset removes NETIF_F_NETNS_LOCAL
from vxlan, ppp and bridge devices.

Rami Rosen (3):
  ppp: remove NETIF_F_NETNS_LOCAL from ppp device features.
  bridge: remove NETIF_F_NETNS_LOCAL from bridge device.
  vxlan: remove NETIF_F_NETNS_LOCAL from vxlan device features.

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

-- 
1.7.11.7

             reply	other threads:[~2013-01-03  9:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  9:25 Rami Rosen [this message]
2013-01-03  9:25 ` [RFC PATCH net-next 1/3] ppp: remove NETIF_F_NETNS_LOCAL from ppp device features Rami Rosen
2013-01-03  9:25 ` [RFC PATCH net-next 2/3] bridge: remove NETIF_F_NETNS_LOCAL from bridge " Rami Rosen
2013-01-03  9:25 ` [RFC PATCH net-next 3/3] vxlan: remove NETIF_F_NETNS_LOCAL from vxlan " Rami Rosen
2013-01-03 15:45   ` Stephen Hemminger

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=1357205121-4700-1-git-send-email-ramirose@gmail.com \
    --to=ramirose@gmail.com \
    --cc=davem@davemloft.net \
    --cc=ebiederm@xmission.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.