[ovs-git] [openvswitch/ovs] a9e695: datapath-windows: Account for VLAN tag in tunnel D...

[GitHub]

  Branch: refs/heads/master
  Home:   https://github.com/openvswitch/ovs
  Commit: a9e6958101d082dbbdc096d01a803ab3a3eca549
      https://github.com/openvswitch/ovs/commit/a9e6958101d082dbbdc096d01a803ab3a3eca549
  Author: Shashank Ram <rams at vmware.com>
  Date:   2017-11-28 (Tue, 28 Nov 2017)

  Changed paths:
    M datapath-windows/ovsext/Geneve.c
    M datapath-windows/ovsext/Geneve.h
    M datapath-windows/ovsext/Gre.c
    M datapath-windows/ovsext/Gre.h
    M datapath-windows/ovsext/Offload.c
    M datapath-windows/ovsext/Offload.h
    M datapath-windows/ovsext/Stt.c
    M datapath-windows/ovsext/Stt.h
    M datapath-windows/ovsext/Vxlan.c
    M datapath-windows/ovsext/Vxlan.h

  Log Message:
  -----------
  datapath-windows: Account for VLAN tag in tunnel Decap

Decap functions for tunneling protocols do not compute
the packet header offsets correctly when there is a VLAN
tag in the L2 header. This results in incorrect checksum
computation causing the packet to be dropped.

This patch adds support to account for the VLAN tag in the
packet if its present, and makes use of the OvsExtractLayers()
function to correctly compute the header offsets for different
layers.

Testing done:
- Tested Geneve, STT, Vxlan and Gre and verified that there
  are no regressions.
- Verified that packets with VLAN tags are correctly handled
  in the decap code of all tunneling protocols. Previously,
  this would result in packet drops due to invalid checksums
  being computed.
- Verified that non-VLAN tagged packets are handled correctly.

Signed-off-by: Shashank Ram <rams at vmware.com>
Acked-by: Anand Kumar <kumaranand at vmware.com>
Signed-off-by: Alin Gabriel Serdean <aserdean at ovn.org>