diff options
| author | Eric Dumazet <[email protected]> | 2017-08-16 18:09:12 +0000 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2017-08-16 23:28:47 +0000 |
| commit | c780a049f9bf442314335372c9abc4548bfe3e44 (patch) | |
| tree | 9bfe8c76f75ea6d1dbc52efa95ff294d80d58c8a /net/unix/af_unix.c | |
| parent | ptr_ring: use kmalloc_array() (diff) | |
| download | kernel-c780a049f9bf442314335372c9abc4548bfe3e44.tar.gz kernel-c780a049f9bf442314335372c9abc4548bfe3e44.zip | |
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 <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions