summaryrefslogtreecommitdiffstats
path: root/drivers/media/rc
diff options
context:
space:
mode:
authorTom Herbert <therbert@google.com>2014-09-09 11:23:14 -0700
committerDavid S. Miller <davem@davemloft.net>2014-09-09 21:29:33 -0700
commit03d56daafe9d4e04a8a0d305789cd3eda250746b (patch)
tree6ecf406c07b9ce8dde6b059e4c88889402115ed3 /drivers/media/rc
parentfe3881cf7e09dfb93e4a4c65f44e2d92f92d0022 (diff)
downloadop-kernel-dev-03d56daafe9d4e04a8a0d305789cd3eda250746b.zip
op-kernel-dev-03d56daafe9d4e04a8a0d305789cd3eda250746b.tar.gz
ipv6: Clear flush_id to make GRO work
In TCP gro we check flush_id which is derived from the IP identifier. In IPv4 gro path the flush_id is set with the expectation that every matched packet increments IP identifier. In IPv6, the flush_id is never set and thus is uinitialized. What's worse is that in IPv6 over IPv4 encapsulation, the IP identifier is taken from the outer header which is currently not incremented on every packet for Linux stack, so GRO in this case never matches packets (identifier is not increasing). This patch clears flush_id for every time for a matched packet in IPv6 gro_receive. We need to do this each time to overwrite the setting that would be done in IPv4 gro_receive per the outer header in IPv6 over Ipv4 encapsulation. Signed-off-by: Tom Herbert <therbert@google.com> Signed-off-by: Eric Dumazet <edumazet@google.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/media/rc')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud