From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Yang, Qiming" <qiming.yang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH] net/iavf: fix mask not allowed issue
Date: Wed, 18 May 2022 04:45:54 +0000 [thread overview]
Message-ID: <PH7PR11MB5982EFD9DC04A8F5CB7644E2D7D19@PH7PR11MB5982.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220516020319.2430990-1-qiming.yang@intel.com>
> -----Original Message-----
> From: Yang, Qiming <qiming.yang@intel.com>
> Sent: Monday, May 16, 2022 10:03 AM
> To: dev@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>
> Cc: Yang, Qiming <qiming.yang@intel.com>; stable@dpdk.org
> Subject: [PATCH] net/iavf: fix mask not allowed issue
>
How about "fix invalid flow mask handling"
> Only zero-mask and full-mask for IPv4/UDP/TCP/SCTP addr/port are supported
> in current code. Otherwise will return failure when parse pattern.
>
> Fixes: d5eb3e600d9e ("net/iavf: support flow director basic rule")
> Cc: stable@dpdk.org
>
> Signed-off-by: Qiming Yang <qiming.yang@intel.com>
> ---
> drivers/net/iavf/iavf_fdir.c | 150 +++++++++++++++++++++--------------
> 1 file changed, 89 insertions(+), 61 deletions(-)
>
> diff --git a/drivers/net/iavf/iavf_fdir.c b/drivers/net/iavf/iavf_fdir.c index
> b63aaca91d..356bca8d41 100644
> --- a/drivers/net/iavf/iavf_fdir.c
> +++ b/drivers/net/iavf/iavf_fdir.c
> @@ -802,6 +802,14 @@ iavf_fdir_parse_pattern(__rte_unused struct
> iavf_adapter *ad,
> return -rte_errno;
> }
>
> + /* Mask for IPv4 src/dst addrs not supported */
> + if (ipv4_mask->hdr.src_addr &&
> + ipv4_mask->hdr.src_addr != UINT32_MAX)
> + return -rte_errno;
> + if (ipv4_mask->hdr.dst_addr &&
> + ipv4_mask->hdr.dst_addr != UINT32_MAX)
> + return -rte_errno;
Do we need to call rte_flow_error_set before return -rte_errno?
prev parent reply other threads:[~2022-05-18 4:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 2:03 Qiming Yang
2022-05-18 4:45 ` Zhang, Qi Z [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=PH7PR11MB5982EFD9DC04A8F5CB7644E2D7D19@PH7PR11MB5982.namprd11.prod.outlook.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
/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).