net/mlx5e: Fix wrong source vport matching on tunnel rule
authorAriel Levkovich <lariel@nvidia.com>
Tue, 15 Mar 2022 16:20:48 +0000 (18:20 +0200)
committerSaeed Mahameed <saeedm@nvidia.com>
Wed, 4 May 2022 07:00:01 +0000 (00:00 -0700)
commitcb0d54cbf94866b48a73e10a73a55655f808cc7c
treece3d4212b088027d9bd45bf933a21d2a4a1deb2d
parent0a806ecc4023fcf393fcc1093f4a532813ca4124
net/mlx5e: Fix wrong source vport matching on tunnel rule

When OVS internal port is the vtep device, the first decap
rule is matching on the internal port's vport metadata value
and then changes the metadata to be the uplink's value.

Therefore, following rules on the tunnel, in chain > 0, should
avoid matching on internal port metadata and use the uplink
vport metadata instead.

Select the uplink's metadata value for the source vport match
in case the rule is in chain greater than zero, even if the tunnel
route device is internal port.

Fixes: 166f431ec6be ("net/mlx5e: Add indirect tc offload of ovs internal port")
Signed-off-by: Ariel Levkovich <lariel@nvidia.com>
Reviewed-by: Maor Dickman <maord@nvidia.com>
Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c