[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20161021.135828.966455231750113733.davem@davemloft.net>
Date: Fri, 21 Oct 2016 13:58:28 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jarod@...hat.com
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
asbjorn@...jorn.st, parameswaran.r7@...il.com
Subject: Re: [PATCH net] net: remove MTU limits on a few ether_setup callers
From: Jarod Wilson <jarod@...hat.com>
Date: Thu, 20 Oct 2016 23:25:27 -0400
> These few drivers call ether_setup(), but have no ndo_change_mtu, and thus
> were overlooked for changes to MTU range checking behavior. They
> previously had no range checks, so for feature-parity, set their min_mtu
> to 0 and max_mtu to ETH_MAX_MTU (65535), instead of the 68 and 1500
> inherited from the ether_setup() changes. Fine-tuning can come after we get
> back to full feature-parity here.
>
> CC: netdev@...r.kernel.org
> Reported-by: Asbjoern Sloth Toennesen <asbjorn@...jorn.st>
> CC: Asbjoern Sloth Toennesen <asbjorn@...jorn.st>
> CC: R Parameswaran <parameswaran.r7@...il.com>
> Signed-off-by: Jarod Wilson <jarod@...hat.com>
Applied.
Please use "[PATCH net-next]" in your subject line when a patch
targets net-next.
Powered by blists - more mailing lists