All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Raslan Darawsheh <rasland@nvidia.com>,
	Eli Britstein <elibr@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Dekel Peled <dekelp@nvidia.com>, Ori Kam <orika@nvidia.com>,
	Matan Azrad <matan@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Shahaf Shuler <shahafs@nvidia.com>, Asaf Penso <asafp@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH V3 1/1] net/mlx5: fix IPv6 next proto validation
Date: Thu, 22 Oct 2020 17:38:43 +0100	[thread overview]
Message-ID: <fd08203d-ec31-297b-ba8b-a832182ad398@intel.com> (raw)
In-Reply-To: <DM6PR12MB2748540438B17CF028563153CF1D0@DM6PR12MB2748.namprd12.prod.outlook.com>

On 10/22/2020 11:01 AM, Raslan Darawsheh wrote:
> Hi,
> 
>> -----Original Message-----
>> From: Eli Britstein <elibr@nvidia.com>
>> Sent: Thursday, October 22, 2020 11:26 AM
>> To: dev@dpdk.org
>> Cc: Dekel Peled <dekelp@nvidia.com>; Ori Kam <orika@nvidia.com>; Matan
>> Azrad <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>; Slava
>> Ovsiienko <viacheslavo@nvidia.com>; Shahaf Shuler <shahafs@nvidia.com>;
>> Asaf Penso <asafp@nvidia.com>; Eli Britstein <elibr@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 <elibr@nvidia.com>
>> Acked-by: Dekel Peled <dekelp@nvidia.com>
>> Acked-by: Matan Azrad <matan@nvidia.com>
> 
> 
> Patch applied to next-net-mlx,
> 

Squashed into relevant commit in next-net, thanks.

      reply	other threads:[~2020-10-22 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-20 12:09 [dpdk-dev] [PATCH] net/mlx5: fix IPv6 next proto validation Dekel Peled
2020-10-20 13:19 ` [dpdk-dev] [PATCH V2 1/1] " Eli Britstein
2020-10-20 13:49   ` Eli Britstein
2020-10-21 14:22   ` Matan Azrad
2020-10-22  8:26     ` [dpdk-dev] [PATCH V3 " Eli Britstein
2020-10-22 10:01       ` Raslan Darawsheh
2020-10-22 16:38         ` Ferruh Yigit [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fd08203d-ec31-297b-ba8b-a832182ad398@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=asafp@nvidia.com \
    --cc=dekelp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=elibr@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=viacheslavo@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.