ipv4: better IP_MAX_MTU enforcement
authorEric Dumazet <edumazet@google.com>
Wed, 16 Aug 2017 18:09:12 +0000 (11:09 -0700)
committerDavid S. Miller <davem@davemloft.net>
Wed, 16 Aug 2017 23:28:47 +0000 (16:28 -0700)
commitc780a049f9bf442314335372c9abc4548bfe3e44
tree9bfe8c76f75ea6d1dbc52efa95ff294d80d58c8a
parent81fbfe8adaf38d4f5a98c19bebfd41c5d6acaee8
ipv4: better IP_MAX_MTU enforcement

While working on yet another syzkaller report, I found
that our IP_MAX_MTU enforcements were not properly done.

gcc seems to reload dev->mtu for min(dev->mtu, IP_MAX_MTU), and
final result can be bigger than IP_MAX_MTU :/

This is a problem because device mtu can be changed on other cpus or
threads.

While this patch does not fix the issue I am working on, it is
probably worth addressing it.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
include/net/ip.h
net/ipv4/route.c