patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: matan@nvidia.com, viacheslavo@nvidia.com, orika@nvidia.com,
	Suanming Mou <suanmingm@nvidia.com>,
	Rongwei Liu <rongweil@nvidia.com>
Cc: stable@dpdk.org, rasland@nvidia.com
Subject: Re: [PATCH 22.11] net/mlx5: fix testpmd crash by action template
Date: Mon, 06 Mar 2023 11:55:49 +0100	[thread overview]
Message-ID: <32273080.6xKfjbll68@thomas> (raw)
In-Reply-To: <20230306091526.2210924-1-rongweil@nvidia.com>

This patch is not specific to testpmd.
We should drop "testpmd" from the title.
Something like "fix crash on flow action template failure"


06/03/2023 10:15, Rongwei Liu:
> When action template creation fails the testpmd expects error
> details.
> The driver did not set the error structure and testpmd failed with a
> segmentation fault.
> 
> Fixes: 836b5c9b5e0e ("net/mlx5: add action template management")
> Cc: stable@dpdk.org
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
>  drivers/net/mlx5/mlx5_flow_hw.c | 15 ++++++++++++++-
>  1 file changed, 14 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c
> index b4a80f977f..9e5f263ccf 100644
> --- a/drivers/net/mlx5/mlx5_flow_hw.c
> +++ b/drivers/net/mlx5/mlx5_flow_hw.c
> @@ -4946,6 +4950,9 @@ flow_hw_actions_template_create(struct rte_eth_dev *dev,
>  			mlx5dr_action_template_destroy(at->tmpl);
>  		mlx5_free(at);
>  	}
> +	rte_flow_error_set(error, rte_errno,
> +			   RTE_FLOW_ERROR_TYPE_UNSPECIFIED, NULL,
> +			   "Failed to create action template");
>  	return NULL;
>  }
> 






  reply	other threads:[~2023-03-06 10:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06  9:15 Rongwei Liu
2023-03-06 10:55 ` Thomas Monjalon [this message]
2023-03-06 11:04   ` [PATCH 22.11] net/mlx5: fix crash on action template failure Rongwei Liu
2023-04-08 13:31     ` Xueming(Steven) Li

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=32273080.6xKfjbll68@thomas \
    --to=thomas@monjalon.net \
    --cc=matan@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@nvidia.com \
    --cc=rongweil@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=suanmingm@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 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).