[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170306135436.GD1822@nanopsycho.orion>
Date: Mon, 6 Mar 2017 14:54:36 +0100
From: Jiri Pirko <jiri@...nulli.us>
To: Jarod Wilson <jarod@...hat.com>
Cc: linux-kernel@...r.kernel.org, Cong Wang <xiyou.wangcong@...il.com>,
netdev@...r.kernel.org
Subject: Re: [PATCH net] team: use ETH_MAX_MTU as max mtu
Mon, Mar 06, 2017 at 02:48:58PM CET, jarod@...hat.com wrote:
>This restores the ability to set a team device's mtu to anything higher
>than 1500. Similar to the reported issue with bonding, the team driver
>calls ether_setup(), which sets an initial max_mtu of 1500, while the
>underlying hardware can handle something much larger. Just set it to
>ETH_MAX_MTU to support all possible values, and the limitations of the
>underlying devices will prevent setting anything too large.
>
>Fixes: 91572088e3fd ("net: use core MTU range checking in core net infra")
>CC: Cong Wang <xiyou.wangcong@...il.com>
>CC: Jiri Pirko <jiri@...nulli.us>
>CC: netdev@...r.kernel.org
>Signed-off-by: Jarod Wilson <jarod@...hat.com>
Acked-by: Jiri Pirko <jiri@...lanox.com>
Powered by blists - more mailing lists