Searched hist:c780a049 (Results 1 – 2 of 2) sorted by relevance
/openbmc/linux/include/net/ |
H A D | ip.h | c780a049 Wed Aug 16 13:09:12 CDT 2017 Eric Dumazet <edumazet@google.com> 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> c780a049 Wed Aug 16 13:09:12 CDT 2017 Eric Dumazet <edumazet@google.com> 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>
|
/openbmc/linux/net/ipv4/ |
H A D | route.c | c780a049 Wed Aug 16 13:09:12 CDT 2017 Eric Dumazet <edumazet@google.com> 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> c780a049 Wed Aug 16 13:09:12 CDT 2017 Eric Dumazet <edumazet@google.com> 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>
|