From: Raslan Darawsheh <rasland@mellanox.com>
To: Michael Baum <michaelba@mellanox.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@mellanox.com>,
Slava Ovsiienko <viacheslavo@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix enum misusing for steering registers
Date: Wed, 22 Jul 2020 15:30:47 +0000 [thread overview]
Message-ID: <AM0PR05MB6707DE48A146596D3EECEECBC2790@AM0PR05MB6707.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <1595332641-6144-1-git-send-email-michaelba@mellanox.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Michael Baum
> Sent: Tuesday, July 21, 2020 2:57 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@mellanox.com>; Slava Ovsiienko
> <viacheslavo@mellanox.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH] net/mlx5: fix enum misusing for steering
> registers
>
> The mlx5_flow_action_copy_mreg structure contains a field called src
> type enum modify_reg, similarly the mlx5_rte_flow_item_tag field
> contains a field called id type enum modify_reg.
> The enum modify_reg variable represents different registers in the
> system and it also has a field called REG_NONE whose value is 0 which
> means that the register does not exist.
>
> The flow_mreg_add_copy_action function sets a variable of struct
> mlx5_flow_action_copy_mreg type, and initializes the src field to be 0.
> similarly the flow_create_split_metadata function sets a variable of
> struct mlx5_rte_flow_item_tag type and initializes the id field to be 0.
> In both functions, they initialize a enum modify_reg type variable with
> an int type value while modify_reg has an appropriate field for that
> value (REG_NONE).
>
> Replace assigning 0 with REG_NONE in both functions.
>
> Fixes: dd3c774f6ffb ("net/mlx5: add metadata register copy table")
> Fixes: 71e254bc0294 ("net/mlx5: split Rx flows to provide metadata copy")
> Cc: stable@dpdk.org
>
> Signed-off-by: Michael Baum <michaelba@mellanox.com>
> Acked-by: Matan Azrad <matan@mellanox.com>
> ---
> drivers/net/mlx5/mlx5_flow.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
> index b56bee4..aba8f41 100644
> --- a/drivers/net/mlx5/mlx5_flow.c
> +++ b/drivers/net/mlx5/mlx5_flow.c
> @@ -3011,7 +3011,7 @@ struct mlx5_flow_tunnel_info {
> };
> struct mlx5_flow_action_copy_mreg cp_mreg = {
> .dst = REG_B,
> - .src = 0,
> + .src = REG_NONE,
> };
> struct rte_flow_action_jump jump = {
> .group = MLX5_FLOW_MREG_ACT_TABLE_GROUP,
> @@ -4067,7 +4067,7 @@ struct mlx5_flow_tunnel_info {
> /* Internal PMD action to set register. */
> struct mlx5_rte_flow_item_tag q_tag_spec = {
> .data = qrss_id,
> - .id = 0,
> + .id = REG_NONE,
> };
> struct rte_flow_item q_items[] = {
> {
> --
> 1.8.3.1
Patch applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2020-07-22 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 11:57 Michael Baum
2020-07-22 15:30 ` 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=AM0PR05MB6707DE48A146596D3EECEECBC2790@AM0PR05MB6707.eurprd05.prod.outlook.com \
--to=rasland@mellanox.com \
--cc=dev@dpdk.org \
--cc=matan@mellanox.com \
--cc=michaelba@mellanox.com \
--cc=stable@dpdk.org \
--cc=viacheslavo@mellanox.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).