summaryrefslogtreecommitdiffstats
path: root/drivers/clk
diff options
context:
space:
mode:
authorK. Den <den@klaipeden.com>2017-08-01 01:05:39 +0900
committerDavid S. Miller <davem@davemloft.net>2017-08-01 16:09:14 -0700
commit1bff8a0c1f8c236209ee369b7952751c04eaa71a (patch)
tree23acac718b58acbd3953b5f7be560d0def0ee0b6 /drivers/clk
parentbe73b3043bf465455d4c9b88f68e03b6447bcfb0 (diff)
downloadlinux-stable-1bff8a0c1f8c236209ee369b7952751c04eaa71a.tar.gz
linux-stable-1bff8a0c1f8c236209ee369b7952751c04eaa71a.tar.bz2
linux-stable-1bff8a0c1f8c236209ee369b7952751c04eaa71a.zip
gue: fix remcsum when GRO on and CHECKSUM_PARTIAL boundary is outer UDP
In the case that GRO is turned on and the original received packet is CHECKSUM_PARTIAL, if the outer UDP header is exactly at the last csum-unnecessary point, which for instance could occur if the packet comes from another Linux guest on the same Linux host, we have to do either remcsum_adjust or set up CHECKSUM_PARTIAL again with its csum_start properly reset considering RCO. However, since b7fe10e5ebac ("gro: Fix remcsum offload to deal with frags in GRO") that barrier in such case could be skipped if GRO turned on, hence we pass over it and the inner L4 validation mistakenly reckons it as a bad csum. This patch makes remcsum_offload being reset at the same time of GRO remcsum cleanup, so as to make it work in such case as before. Fixes: b7fe10e5ebac ("gro: Fix remcsum offload to deal with frags in GRO") Signed-off-by: Koichiro Den <den@klaipeden.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/clk')
0 files changed, 0 insertions, 0 deletions