From: "Yang, Qiming" <qiming.yang@intel.com>
To: "Wang, Ying A" <ying.a.wang@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/3] net/ice: fix flow get inputset check
Date: Thu, 18 Jul 2019 02:33:23 +0000 [thread overview]
Message-ID: <F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A50615B@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1563413923-404004-2-git-send-email-ying.a.wang@intel.com>
It's no need to add RTE_FLOW_ITEM_TYPE_VOID because we have skipped all the VOID items.
-----Original Message-----
From: Wang, Ying A
Sent: Thursday, July 18, 2019 9:39 AM
To: Zhang, Qi Z <qi.z.zhang@intel.com>
Cc: Yang, Qiming <qiming.yang@intel.com>; dev@dpdk.org; Wang, Ying A <ying.a.wang@intel.com>; stable@dpdk.org
Subject: [PATCH 1/3] net/ice: fix flow get inputset check
ice_get_flow_field should not set error if item->type is RTE_FLOW_ITEM_TYPE_VOID.
This patch fixes this issue.
Fixes: d76116a4678f ("net/ice: add generic flow API")
Cc: stable@dpdk.org
Signed-off-by: Wang Ying A <ying.a.wang@intel.com>
---
drivers/net/ice/ice_generic_flow.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/net/ice/ice_generic_flow.c b/drivers/net/ice/ice_generic_flow.c
index c2931a1..464f6ec 100644
--- a/drivers/net/ice/ice_generic_flow.c
+++ b/drivers/net/ice/ice_generic_flow.c
@@ -465,7 +465,7 @@ static uint64_t ice_get_flow_field(const struct rte_flow_item pattern[],
case RTE_FLOW_ITEM_TYPE_NVGRE:
nvgre_spec = item->spec;
nvgre_mask = item->mask;
- /* Check if VXLAN item is used to describe protocol.
+ /* Check if NVGRE item is used to describe protocol.
* If yes, both spec and mask should be NULL.
* If no, both spec and mask shouldn't be NULL.
*/
@@ -480,6 +480,8 @@ static uint64_t ice_get_flow_field(const struct rte_flow_item pattern[],
is_tunnel = 1;
break;
+ case RTE_FLOW_ITEM_TYPE_VOID:
+ break;
default:
rte_flow_error_set(error, EINVAL,
RTE_FLOW_ERROR_TYPE_ITEM,
--
1.8.3.1
next prev parent reply other threads:[~2019-07-18 2:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1563413923-404004-1-git-send-email-ying.a.wang@intel.com>
2019-07-18 1:38 ` Wang Ying A
2019-07-18 2:33 ` Yang, Qiming [this message]
2019-07-18 2:40 ` Wang, Ying A
2019-07-18 2:46 ` Yang, Qiming
2019-07-18 2:52 ` Wang, Ying A
2019-07-19 0:31 ` Zhang, Qi Z
2019-07-18 1:38 ` [dpdk-stable] [PATCH 2/3] net/ice: fix flow action validation Wang Ying A
2019-07-18 3:06 ` Yang, Qiming
2019-07-19 0:34 ` Zhang, Qi Z
2019-07-18 9:08 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-07-18 1:38 ` [dpdk-stable] [PATCH 3/3] net/ice: add flow ipv6 tc support Wang Ying A
2019-07-18 3:06 ` Yang, Qiming
2019-07-19 0:48 ` Zhang, Qi Z
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=F5DF4F0E3AFEF648ADC1C3C33AD4DBF17A50615B@SHSMSX101.ccr.corp.intel.com \
--to=qiming.yang@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=ying.a.wang@intel.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).