diff options
author | Eric Dumazet <edumazet@google.com> | 2017-08-16 11:09:12 -0700 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2017-08-30 10:19:19 +0200 |
commit | 1bd54371388c0c1e24e3ffa8afde9e130c5799b9 (patch) | |
tree | 796335838a30430ad4d09954ba8c0acaa8a0371c /net/tipc/netlink_compat.c | |
parent | 7e1fe0062c24b1cdfb58fb494d03741a6b0a4ac8 (diff) |
ipv4: better IP_MAX_MTU enforcement
[ Upstream commit c780a049f9bf442314335372c9abc4548bfe3e44 ]
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'net/tipc/netlink_compat.c')
0 files changed, 0 insertions, 0 deletions