From: David Ahern <dsahern@gmail.com>
To: Mike Manning <mmanning@vyatta.mail-att.com>, netdev@vger.kernel.org
Subject: Re: [PATCH] net: allow interface to be set into vrf if a vif in same vrf
Date: Mon, 26 Feb 2018 09:53:04 -0700 [thread overview]
Message-ID: <18fbff9e-b44f-1656-e3cb-12bef4dc8733@gmail.com> (raw)
In-Reply-To: <1519663736-28904-1-git-send-email-mmanning@vyatta.mail-att.com>
On 2/26/18 9:48 AM, Mike Manning wrote:
> Setting an interface into a vrf fails with 'RTNETLINK answers: File
> exists' if one of its vifs is already in the same vrf. As the vrf is an
> upper device of the vif, it is also showing up as an upper device of
> the interface itself. The solution is to restrict this check to devices
> other than master. As only one master device can be linked to a device,
> in this case the check is for the upper device (vrf) to be linked to as
> being the master device rather than any other upper device.
I'm not understanding what you mean by vif in this context. Can you
elaborate and show an example set of commands?
>
> Signed-off-by: Mike Manning <mmanning@att.com>
> ---
> net/core/dev.c | 14 +++++++++-----
> 1 file changed, 9 insertions(+), 5 deletions(-)
>
> diff --git a/net/core/dev.c b/net/core/dev.c
> index d4362be..2cedf52 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -6396,6 +6396,7 @@ static int __netdev_upper_dev_link(struct net_device *dev,
> .linking = true,
> .upper_info = upper_info,
> };
> + struct net_device *master_dev;
> int ret = 0;
>
> ASSERT_RTNL();
> @@ -6407,11 +6408,14 @@ static int __netdev_upper_dev_link(struct net_device *dev,
> if (netdev_has_upper_dev(upper_dev, dev))
> return -EBUSY;
>
> - if (netdev_has_upper_dev(dev, upper_dev))
> - return -EEXIST;
> -
> - if (master && netdev_master_upper_dev_get(dev))
> - return -EBUSY;
> + if (!master) {
> + if (netdev_has_upper_dev(dev, upper_dev))
> + return -EEXIST;
> + } else {
> + master_dev = netdev_master_upper_dev_get(dev);
> + if (master_dev)
> + return master_dev == upper_dev ? -EEXIST : -EBUSY;
> + }
>
> ret = call_netdevice_notifiers_info(NETDEV_PRECHANGEUPPER,
> &changeupper_info.info);
>
next prev parent reply other threads:[~2018-02-26 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 16:48 [PATCH] net: allow interface to be set into vrf if a vif in same vrf Mike Manning
2018-02-26 16:53 ` David Ahern [this message]
2018-03-01 18:28 ` David Miller
2018-03-01 18:30 ` David Ahern
[not found] <61cddbff-8a2b-426e-9d43-29ab2ebb2493@mail.eng.vyatta.net>
[not found] ` <f1ba6938-588c-1deb-c5da-b698301759cf@vyatta.att-mail.com>
2018-02-26 20:43 ` David Ahern
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=18fbff9e-b44f-1656-e3cb-12bef4dc8733@gmail.com \
--to=dsahern@gmail.com \
--cc=mmanning@vyatta.mail-att.com \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).