summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorWillem de Bruijn <willemb@google.com>2017-08-08 14:22:55 -0400
committerDavid S. Miller <davem@davemloft.net>2017-08-08 21:39:01 -0700
commit8d63bee643f1fb53e472f0e135cae4eb99d62d19 (patch)
tree6576b105739a9652afc6c8342d6922e2df476790 /drivers
parentbbae08e592706dc32e5c7c97827b13c1c178668b (diff)
downloadlinux-stable-8d63bee643f1fb53e472f0e135cae4eb99d62d19.tar.gz
linux-stable-8d63bee643f1fb53e472f0e135cae4eb99d62d19.tar.bz2
linux-stable-8d63bee643f1fb53e472f0e135cae4eb99d62d19.zip
net: avoid skb_warn_bad_offload false positives on UFO
skb_warn_bad_offload triggers a warning when an skb enters the GSO stack at __skb_gso_segment that does not have CHECKSUM_PARTIAL checksum offload set. Commit b2504a5dbef3 ("net: reduce skb_warn_bad_offload() noise") observed that SKB_GSO_DODGY producers can trigger the check and that passing those packets through the GSO handlers will fix it up. But, the software UFO handler will set ip_summed to CHECKSUM_NONE. When __skb_gso_segment is called from the receive path, this triggers the warning again. Make UFO set CHECKSUM_UNNECESSARY instead of CHECKSUM_NONE. On Tx these two are equivalent. On Rx, this better matches the skb state (checksum computed), as CHECKSUM_NONE here means no checksum computed. See also this thread for context: http://patchwork.ozlabs.org/patch/799015/ Fixes: b2504a5dbef3 ("net: reduce skb_warn_bad_offload() noise") Signed-off-by: Willem de Bruijn <willemb@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions