From: Harman Kalra <hkalra@marvell.com>
To: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
Harman Kalra <hkalra@marvell.com>
Cc: <dev@dpdk.org>, <jerinj@marvell.com>,
Amit Prakash Shukla <amitprakashs@marvell.com>
Subject: [PATCH v2 4/5] net/cnxk: fix invalid pattern count
Date: Mon, 24 Jun 2024 17:27:32 +0530 [thread overview]
Message-ID: <20240624115733.191307-4-hkalra@marvell.com> (raw)
In-Reply-To: <20240624115733.191307-1-hkalra@marvell.com>
From: Amit Prakash Shukla <amitprakashs@marvell.com>
Increment nb_pattern count to include RTE_FLOW_ITEM_TYPE_END.
Fixes: aebe8cf310cc ("net/cnxk: create flow on representor ports")
Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
---
V2:
* Added fixes tag
drivers/net/cnxk/cnxk_rep_flow.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/net/cnxk/cnxk_rep_flow.c b/drivers/net/cnxk/cnxk_rep_flow.c
index d26f5aa12c..f1cf81a90c 100644
--- a/drivers/net/cnxk/cnxk_rep_flow.c
+++ b/drivers/net/cnxk/cnxk_rep_flow.c
@@ -171,6 +171,9 @@ populate_vxlan_encap_action_conf(const struct rte_flow_action_vxlan_encap *vxlan
for (; pattern->type != RTE_FLOW_ITEM_TYPE_END; pattern++)
nb_patterns++;
+ /* +1 for RTE_FLOW_ITEM_TYPE_END */
+ nb_patterns++;
+
len = sizeof(uint64_t);
rte_memcpy(vxlan_encap_action_data, &nb_patterns, len);
pattern = vxlan_conf->definition;
--
2.18.0
next prev parent reply other threads:[~2024-06-24 11:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 7:48 [PATCH 1/6] net/cnxk: stale offload flag reset Harman Kalra
2024-06-24 7:48 ` [PATCH 2/6] net/cnxk: add MTU set ops Harman Kalra
2024-06-24 7:48 ` [PATCH 3/6] net/cnxk: add multi seg support in eswitch Harman Kalra
2024-06-24 7:48 ` [PATCH 4/6] net/cnxk: increment number of flow pattern Harman Kalra
2024-06-24 9:14 ` Jerin Jacob
2024-06-24 7:48 ` [PATCH 5/6] net/cnxk: update processing ready message Harman Kalra
2024-06-24 7:48 ` [PATCH 6/6] common/cnxk: flow aginig delaying app shutdown Harman Kalra
2024-06-24 9:13 ` [PATCH 1/6] net/cnxk: stale offload flag reset Jerin Jacob
2024-06-24 11:57 ` [PATCH v2 1/5] net/cnxk: fix " Harman Kalra
2024-06-24 11:57 ` [PATCH v2 2/5] net/cnxk: add MTU set ops Harman Kalra
2024-06-24 11:57 ` [PATCH v2 3/5] net/cnxk: add multi seg support in eswitch Harman Kalra
2024-06-24 11:57 ` Harman Kalra [this message]
2024-06-24 11:57 ` [PATCH v2 5/5] net/cnxk: fix representor port mapping Harman Kalra
2024-06-24 13:24 ` [PATCH v3 1/5] net/cnxk: fix stale offload flag reset Harman Kalra
2024-06-24 13:24 ` [PATCH v3 2/5] net/cnxk: add MTU set ops Harman Kalra
2024-06-24 13:24 ` [PATCH v3 3/5] net/cnxk: add multi seg support in eswitch Harman Kalra
2024-06-24 13:24 ` [PATCH v3 4/5] net/cnxk: fix invalid pattern count Harman Kalra
2024-06-24 13:24 ` [PATCH v3 5/5] net/cnxk: fix representor port mapping Harman Kalra
2024-06-25 9:46 ` Jerin Jacob
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=20240624115733.191307-4-hkalra@marvell.com \
--to=hkalra@marvell.com \
--cc=amitprakashs@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).