From: Jay Vosburgh <jay.vosburgh@canonical.com>
To: Wengang Wang <wen.gang.wang@oracle.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] net: take care of bonding in build_skb_flow_key (v2)
Date: Tue, 12 Jan 2016 12:22:48 -0800 [thread overview]
Message-ID: <12940.1452630168@famine> (raw)
In-Reply-To: <1452070997-10395-1-git-send-email-wen.gang.wang@oracle.com>
Wengang Wang <wen.gang.wang@oracle.com> wrote:
>In a bonding setting, we determines fragment size according to MTU and
>PMTU associated to the bonding master. If the slave finds the fragment
>size is too big, it drops the fragment and calls ip_rt_update_pmtu(),
>passing _skb_ and _pmtu_, trying to update the path MTU.
>Problem is that the target device that function ip_rt_update_pmtu actually
>tries to update is the slave (skb->dev), not the master. Thus since no
>PMTU change happens on master, the fragment size for later packets doesn't
>change so all later fragments/packets are dropped too.
>
>The fix is letting build_skb_flow_key() take care of the transition of
>device index from bonding slave to the master. That makes the master become
>the target device that ip_rt_update_pmtu tries to update PMTU to.
Does the team driver have the equivalent issue?
>Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
>---
> net/ipv4/route.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
>diff --git a/net/ipv4/route.c b/net/ipv4/route.c
>index 85f184e..fffc7e6 100644
>--- a/net/ipv4/route.c
>+++ b/net/ipv4/route.c
>@@ -523,10 +523,18 @@ static void build_skb_flow_key(struct flowi4 *fl4, const struct sk_buff *skb,
> const struct sock *sk)
> {
> const struct iphdr *iph = ip_hdr(skb);
>- int oif = skb->dev->ifindex;
> u8 tos = RT_TOS(iph->tos);
>+ struct net_device *master;
> u8 prot = iph->protocol;
> u32 mark = skb->mark;
>+ int oif;
>+
>+ if (skb->dev->flags & IFF_SLAVE) {
>+ master = netdev_master_upper_dev_get(skb->dev);
>+ oif = master->ifindex;
>+ } else {
>+ oif = skb->dev->ifindex;
>+ }
netdev_master_upper_dev_get() requires RTNL to be held; I don't
see that all callers to build_skb_flow_key will do so.
I also believe the above would dereference a NULL pointer if an
eql device is configured, as it uses IFF_SLAVE but doesn't use the
upper/lower device infrastructure, thus, netdev_master_upper_dev_get()
would likely return NULL for eql.
-J
---
-Jay Vosburgh, jay.vosburgh@canonical.com
next prev parent reply other threads:[~2016-01-12 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 9:03 [PATCH] net: take care of bonding in build_skb_flow_key (v2) Wengang Wang
2016-01-06 9:43 ` zhuyj
2016-01-12 20:22 ` Jay Vosburgh [this message]
2016-01-20 4:56 ` Wengang Wang
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=12940.1452630168@famine \
--to=jay.vosburgh@canonical.com \
--cc=netdev@vger.kernel.org \
--cc=wen.gang.wang@oracle.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;
as well as URLs for NNTP newsgroup(s).