diff options
| author | Tom Herbert <therbert@google.com> | 2015-02-11 03:30:27 +0300 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2015-02-12 02:12:09 +0300 |
| commit | 26c4f7da3e413da697a7beb22ad496390eda7da0 (patch) | |
| tree | 55182c7a68fc4129369ffce2ac30a897cc3d55a1 /net/ipv4/udp_offload.c | |
| parent | 13101602c4a9f653d59af9469040797bc5b361ca (diff) | |
| download | linux-26c4f7da3e413da697a7beb22ad496390eda7da0.tar.xz | |
net: Fix remcsum in GRO path to not change packet
Remote checksum offload processing is currently the same for both
the GRO and non-GRO path. When the remote checksum offload option
is encountered, the checksum field referred to is modified in
the packet. So in the GRO case, the packet is modified in the
GRO path and then the operation is skipped when the packet goes
through the normal path based on skb->remcsum_offload. There is
a problem in that the packet may be modified in the GRO path, but
then forwarded off host still containing the remote checksum option.
A remote host will again perform RCO but now the checksum verification
will fail since GRO RCO already modified the checksum.
To fix this, we ensure that GRO restores a packet to it's original
state before returning. In this model, when GRO processes a remote
checksum option it still changes the checksum per the algorithm
but on return from lower layer processing the checksum is restored
to its original value.
In this patch we add define gro_remcsum structure which is passed
to skb_gro_remcsum_process to save offset and delta for the checksum
being changed. After lower layer processing, skb_gro_remcsum_cleanup
is called to restore the checksum before returning from GRO.
Signed-off-by: Tom Herbert <therbert@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/udp_offload.c')
0 files changed, 0 insertions, 0 deletions