[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <5b81bf8a-4d26-84ac-bd2a-533b1f2a9e24@redhat.com>
Date: Mon, 6 Mar 2017 08:49:35 -0500
From: Jarod Wilson <jarod@...hat.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: Cong Wang <xiyou.wangcong@...il.com>, netdev@...r.kernel.org,
daznis@...il.com, lists2009@...rfbargle.com
Subject: Re: [Patch net] bonding: use ETH_MAX_MTU as max mtu
On 2017-03-06 8:40 AM, Jiri Pirko wrote:
> Mon, Mar 06, 2017 at 02:36:47PM CET, jarod@...hat.com wrote:
>> On 2017-03-02 3:24 PM, Cong Wang wrote:
>>> This restores the ability of setting bond device's mtu to 9000.
>>>
>>> Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
>>> Reported-by: daznis@...il.com
>>> Reported-by: Brad Campbell <lists2009@...rfbargle.com>
>>> Cc: Jarod Wilson <jarod@...hat.com>
>>> Signed-off-by: Cong Wang <xiyou.wangcong@...il.com>
>>
>> Apologies, I'm a bit late to the party, direct CC didn't land in inbox
>> because of duplicate suppression or perhaps a greedy mail filtering rule
>> (*grumble*)... Too late to ack, but yeah, that's necessary. I *think* the
>> team driver may also require the same treatment. It calls ether_setup()
>> without anything setting max_mtu as well.
>
> Jarod, could you please send the fix? Thanks.
Done.
--
Jarod Wilson
jarod@...hat.com
Powered by blists - more mailing lists