From: Sridhar Samudrala <sri@us.ibm.com>
To: Cong Wang <amwang@redhat.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [Patch net-next] vxlan: revert "vxlan: Bypass encapsulation if the destination is local"
Date: Thu, 11 Apr 2013 16:59:59 -0700 [thread overview]
Message-ID: <1365724799.3563.5.camel@sridhar.usor.ibm.com> (raw)
In-Reply-To: <1937058599.2214531.1365659704193.JavaMail.root@redhat.com>
On Thu, 2013-04-11 at 01:55 -0400, Cong Wang wrote:
>
> ----- Original Message -----
> > On 4/10/2013 7:10 PM, Cong Wang wrote:
> > >> - when source and destination endpoints belonging to different vni's
> > >> are on 2 different bridges on the same host. encap bypass is done
> > >> in this scenario by checking if rt_flags has RTCF_LOCAL set. I think
> > >> you must be hitting this path and the following patch should fix
> > >> it by only doing bypass if the source and dest devices belong to
> > >> the same net. Can you try it and see if it fixes your tests?
> > > I just tested it, unfortunately it doesn't work, the bug still exists.
> > >
> > > If you need any other info, please let me know.
> > So does it mean that you are hitting the if condition that does encap
> > bypass
> > even afterthe net_eq() check? Do the tests pass If you comment out the
> > 'if' block?
>
> Yes, after adding a printk inside the 'if' block, I got:
>
> [ 71.456329] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth0
> [ 71.596551] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth1
> [ 72.028574] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth0
> [ 72.436384] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth1
> [ 73.028576] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth0
> [ 73.185134] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth0
> [ 73.436582] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth1
> [ 74.184251] vxlan: dev: vxlan0, dst: 224.8.8.8, dst dev: veth0
>
> It seems the dst dev is the dev which vxlan0 setup on, so
> there is no way to know if the packet is targeted for a different netns
> on the same host, at least I don't find such RTCF_* flag.
OK. i was able to setup vxlan between 2 net namespaces and reproduce
the issue.
The following patch fixes the issue for me. can you try it out?
diff --git a/drivers/net/vxlan.c b/drivers/net/vxlan.c
index 9a64715..d6509de 100644
--- a/drivers/net/vxlan.c
+++ b/drivers/net/vxlan.c
@@ -1013,7 +1013,7 @@ static netdev_tx_t vxlan_xmit_one(struct sk_buff *skb, struct net_device *dev,
}
/* Bypass encapsulation if the destination is local */
- if (rt->rt_flags & RTCF_LOCAL) {
+ if (rt->dst.dev->flags & IFF_LOOPBACK) {
struct vxlan_dev *dst_vxlan;
ip_rt_put(rt);
next prev parent reply other threads:[~2013-04-12 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 9:57 [Patch net-next] vxlan: revert "vxlan: Bypass encapsulation if the destination is local" Cong Wang
2013-04-09 17:16 ` David Miller
2013-04-09 18:08 ` Sridhar Samudrala
2013-04-10 14:29 ` Sergei Shtylyov
2013-04-11 2:10 ` Cong Wang
2013-04-11 4:53 ` Sridhar Samudrala
2013-04-11 5:55 ` Cong Wang
2013-04-11 6:33 ` Sridhar Samudrala
2013-04-11 23:59 ` Sridhar Samudrala [this message]
2013-04-12 8:05 ` Cong Wang
2013-04-12 19:19 ` David Miller
2013-04-12 23:07 ` Sridhar Samudrala
2013-04-12 23:17 ` David Miller
2013-04-15 2:31 ` Cong Wang
2013-04-15 4:20 ` Sridhar Samudrala
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=1365724799.3563.5.camel@sridhar.usor.ibm.com \
--to=sri@us.ibm.com \
--cc=amwang@redhat.com \
--cc=davem@davemloft.net \
--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).