[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170308.222000.2114880882228056038.davem@davemloft.net>
Date: Wed, 08 Mar 2017 22:20:00 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: jarod@...hat.com
Cc: linux-kernel@...r.kernel.org, xiyou.wangcong@...il.com,
jiri@...nulli.us, netdev@...r.kernel.org
Subject: Re: [PATCH net] team: use ETH_MAX_MTU as max mtu
From: Jarod Wilson <jarod@...hat.com>
Date: Mon, 6 Mar 2017 08:48:58 -0500
> 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>
Applied and queued up for -stable, thanks.
Powered by blists - more mailing lists