From: David Ahern <dsa@cumulusnetworks.com>
To: Alexis Bauvin <abauvin@scaleway.com>,
roopa@cumulusnetworks.com, nicolas.dichtel@6wind.com
Cc: netdev@vger.kernel.org, akherbouche@scaleway.com
Subject: Re: [RFC v1 3/3] vxlan: handle underlay VRF changes
Date: Wed, 14 Nov 2018 12:04:50 -0800 [thread overview]
Message-ID: <340a2a1e-947a-eae9-fce5-4e1463ec290f@cumulusnetworks.com> (raw)
In-Reply-To: <20181114093104.93286-4-abauvin@scaleway.com>
On 11/14/18 1:31 AM, Alexis Bauvin wrote:
> diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
> index 7477b5510a04..188c0cdb8838 100644
> --- a/drivers/net/vxlan.c
> +++ b/drivers/net/vxlan.c
> @@ -208,6 +208,18 @@ static inline struct vxlan_rdst *first_remote_rtnl(struct vxlan_fdb *fdb)
> return list_first_entry(&fdb->remotes, struct vxlan_rdst, list);
> }
>
> +static int vxlan_is_in_l3mdev_chain(struct net_device *chain,
> + struct net_device *dev)
> +{
> + if (!chain)
> + return 0;
> +
> + if (chain->ifindex == dev->ifindex)
> + return 1;
> + return vxlan_is_in_l3mdev_chain(netdev_master_upper_dev_get(chain),
> + dev);
l3mdev_master_dev_rcu
next prev parent reply other threads:[~2018-11-15 6:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181114093104.93286-1-abauvin@scaleway.com>
[not found] ` <20181114093104.93286-2-abauvin@scaleway.com>
2018-11-14 16:07 ` [RFC v1 1/3] udp_tunnel: add config option to bind to a device Nicolas Dichtel
2018-11-14 17:22 ` Alexis Bauvin
[not found] ` <20181114093104.93286-3-abauvin@scaleway.com>
2018-11-14 19:58 ` [RFC v1 2/3] vxlan: add support for underlay in non-default VRF David Ahern
2018-11-15 10:05 ` Alexis Bauvin
2018-11-16 7:37 ` David Ahern
2018-11-16 10:41 ` Alexis Bauvin
2018-11-16 16:31 ` David Ahern
[not found] ` <20181114093104.93286-4-abauvin@scaleway.com>
2018-11-14 20:04 ` David Ahern [this message]
2018-11-15 10:06 ` [RFC v1 3/3] vxlan: handle underlay VRF changes Alexis Bauvin
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=340a2a1e-947a-eae9-fce5-4e1463ec290f@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=abauvin@scaleway.com \
--cc=akherbouche@scaleway.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=roopa@cumulusnetworks.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox