On 10/22/2020 11:01 AM, Raslan Darawsheh wrote:
Hi,-----Original Message----- From: Eli Britstein <el...@nvidia.com> Sent: Thursday, October 22, 2020 11:26 AM To: dev@dpdk.org Cc: Dekel Peled <dek...@nvidia.com>; Ori Kam <or...@nvidia.com>; Matan Azrad <ma...@nvidia.com>; Raslan Darawsheh <rasl...@nvidia.com>; Slava Ovsiienko <viachesl...@nvidia.com>; Shahaf Shuler <shah...@nvidia.com>; Asaf Penso <as...@nvidia.com>; Eli Britstein <el...@nvidia.com> Subject: [PATCH V3 1/1] net/mlx5: fix IPv6 next proto validation Previous patch added validation of the IPv6 next proto field, in order to overcome a known limitation. One of the values checked is IPPROTO_HOPOPTS, which is defined as 0. If proto field is not specified for matching, or mask=0, as in the following, a wrong validation takes place. flow create 0 ingress pattern eth / ipv6 has_frag_ext is 0 / end actions drop / end Fix the validation only on proto asked by the user. Fixes: 92be60e1b541 ("net/mlx5: enforce limitation on IPv6 next proto") Signed-off-by: Eli Britstein <el...@nvidia.com> Acked-by: Dekel Peled <dek...@nvidia.com> Acked-by: Matan Azrad <ma...@nvidia.com>Patch applied to next-net-mlx,
Squashed into relevant commit in next-net, thanks.
