diff options
| author | Stefan Richter <stefanr@s5r6.in-berlin.de> | 2016-10-23 16:29:03 +0200 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2016-10-26 17:28:50 -0400 |
| commit | 5d48f00d836a628c695c6e3f96881d73641f6a2f (patch) | |
| tree | d07a89e6ba1d5086fbdc60ab4476fcf5186c58b1 /scripts | |
| parent | e2897b8238ab8fdee067cfe472dd52a3414d5716 (diff) | |
| download | linux-5d48f00d836a628c695c6e3f96881d73641f6a2f.tar.gz linux-5d48f00d836a628c695c6e3f96881d73641f6a2f.tar.bz2 linux-5d48f00d836a628c695c6e3f96881d73641f6a2f.zip | |
firewire: net: fix maximum possible MTU
Commit b3e3893e1253 ("net: use core MTU range checking in misc drivers")
mistakenly introduced an upper limit for firewire-net's MTU based on the
local link layer controller's reception capability. Revert this. Neither
RFC 2734 nor our implementation impose any particular upper limit.
Actually, to be on the safe side and to make the code explicit, set
ETH_MAX_MTU = 65535 as upper limit now.
(I replaced sizeof(struct rfc2734_header) by the equivalent
RFC2374_FRAG_HDR_SIZE in order to avoid distracting long/int conversions.)
Fixes: b3e3893e1253('net: use core MTU range checking in misc drivers')
CC: netdev@vger.kernel.org
CC: linux1394-devel@lists.sourceforge.net
CC: Jarod Wilson <jarod@redhat.com>
Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
Acked-by: Jarod Wilson <jarod@redhat.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions