patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Matan Azrad <matan@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Li Zhang <lizh@nvidia.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/mlx5: fix missing RSS validation with meter policy
Date: Tue, 16 Nov 2021 09:25:02 +0000	[thread overview]
Message-ID: <DM4PR12MB5312DA22C2D691C62A8E8069CF999@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211115145121.1663173-1-bingz@nvidia.com>

Hi,

> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Monday, November 15, 2021 4:51 PM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>; Li Zhang
> <lizh@nvidia.com>; stable@dpdk.org
> Subject: [PATCH v2] net/mlx5: fix missing RSS validation with meter policy
> 
> The RSS can be one of the fate actions when creating a meter with policy. In
> the previous implementation, the RSS validation was missed when creating a
> flow rule with such meter due to the fact that a policy meter was created
> firstly and then used in the rule. In the stage of meter creation, no
> rte_flow_item* information was provided.
> 
> A unnecessary RSS expansion might be called since the validation was missed
> and would cause an unexpected error of the rule creation. Even though the
> rule should be rejected from the very beginning, it would cause confusion.
> There might be some other errors when the validation was missed.
> 
> Adding the RSS validation inside the meter action validation will prevent the
> code from continuing when there is a conflict between the items, other
> actions and the policy meter RSS action.
> 
> Fixes: 444320186393 ("net/mlx5: support meter creation with policy")
> Cc: lizh@nvidia.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Reviewed-by: Li Zhang <lizh@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> v2: fix the coding style issue.
> ---

Patch applied to next-net-mlx,

Kindest regards,
Raslan Darawsheh

      reply	other threads:[~2021-11-16  9:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-15 11:35 [PATCH] " Bing Zhao
2021-11-15 14:51 ` [PATCH v2] " Bing Zhao
2021-11-16  9:25   ` Raslan Darawsheh [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=DM4PR12MB5312DA22C2D691C62A8E8069CF999@DM4PR12MB5312.namprd12.prod.outlook.com \
    --to=rasland@nvidia.com \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=lizh@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=stable@dpdk.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).