diff options
author | Eric Dumazet <edumazet@google.com> | 2012-10-08 23:38:50 +0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2012-10-08 23:40:43 +0400 |
commit | 863472454ce50d4ef0929c6aa738cc5d64b84679 (patch) | |
tree | 10a938801074b41e53c8237c92390e745b47a521 /fs/direct-io.c | |
parent | 48cc32d38a52d0b68f91a171a8d00531edc6a46e (diff) | |
download | linux-863472454ce50d4ef0929c6aa738cc5d64b84679.tar.xz |
ipv6: gro: fix PV6_GRO_CB(skb)->proto problem
It seems IPV6_GRO_CB(skb)->proto can be destroyed in skb_gro_receive()
if a new skb is allocated (to serve as an anchor for frag_list)
We copy NAPI_GRO_CB() only (not the IPV6 specific part) in :
*NAPI_GRO_CB(nskb) = *NAPI_GRO_CB(p);
So we leave IPV6_GRO_CB(nskb)->proto to 0 (fresh skb allocation) instead
of IPPROTO_TCP (6)
ipv6_gro_complete() isnt able to call ops->gro_complete()
[ tcp6_gro_complete() ]
Fix this by moving proto in NAPI_GRO_CB() and getting rid of
IPV6_GRO_CB
Signed-off-by: Eric Dumazet <edumazet@google.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/direct-io.c')
0 files changed, 0 insertions, 0 deletions