From: Wengang Wang <wen.gang.wang@oracle.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, sd@queasysnail.net,
jay.vosburgh@canonical.com, zyjzyj2000@gmail.com
Subject: Re: [PATCH] net: take care of bonding in build_skb_flow_key (v4)
Date: Fri, 22 Jan 2016 12:21:28 +0800 [thread overview]
Message-ID: <56A1AE48.4000908@oracle.com> (raw)
In-Reply-To: <20160121083506.GA2251@nanopsycho.orion>
在 2016年01月21日 16:35, Jiri Pirko 写道:
> Thu, Jan 21, 2016 at 06:32:58AM CET, 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.
>>
>> Signed-off-by: Wengang Wang <wen.gang.wang@oracle.com>
>> ---
>> net/ipv4/route.c | 9 +++++++++
>> 1 file changed, 9 insertions(+)
>>
>> diff --git a/net/ipv4/route.c b/net/ipv4/route.c
>> index 85f184e..7e766b5 100644
>> --- a/net/ipv4/route.c
>> +++ b/net/ipv4/route.c
>> @@ -524,10 +524,19 @@ static void build_skb_flow_key(struct flowi4 *fl4, const struct sk_buff *skb,
>> {
>> const struct iphdr *iph = ip_hdr(skb);
>> int oif = skb->dev->ifindex;
>> + struct net_device *master;
>> u8 tos = RT_TOS(iph->tos);
>> u8 prot = iph->protocol;
>> u32 mark = skb->mark;
>>
>> + if (netif_is_bond_slave(skb->dev)) {
>> + rcu_read_lock();
>> + master = netdev_master_upper_dev_get_rcu(skb->dev);
>> + if (master)
>> + oif = master->ifindex;
>> + rcu_read_unlock();
>> + }
> This is certainly not correct as it should not be bond-specific but
> rather generic.
Then what you would suggest to fix it?
> Note that you may have bond over bond or bridge over
> bond or other scenarios, which this patch ignores.
I don't think bond over bond is a good configuration. Do you have a real
use case for that configuration?
thanks,
wengang
next prev parent reply other threads:[~2016-01-22 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 5:32 [PATCH] net: take care of bonding in build_skb_flow_key (v4) Wengang Wang
2016-01-21 8:35 ` Jiri Pirko
2016-01-22 4:21 ` Wengang Wang [this message]
2016-01-22 6:52 ` Jiri Pirko
2016-01-22 8:00 ` Wengang Wang
2016-01-26 7:45 ` zhuyj
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=56A1AE48.4000908@oracle.com \
--to=wen.gang.wang@oracle.com \
--cc=jay.vosburgh@canonical.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=sd@queasysnail.net \
--cc=zyjzyj2000@gmail.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).