Re: [dpdk-dev] [PATCH V2 1/1] net/mlx5: fix IPv6 next proto validation

2020-10-21 Thread Matan Azrad
From: Eli Britstein > 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 valid

Re: [dpdk-dev] [PATCH V2 1/1] net/mlx5: fix IPv6 next proto validation

2020-10-20 Thread Eli Britstein
++ On 10/20/2020 4:19 PM, Eli Britstein wrote: 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,

[dpdk-dev] [PATCH V2 1/1] net/mlx5: fix IPv6 next proto validation

2020-10-20 Thread Eli Britstein
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 ing