From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gregory Etelson <getelson@nvidia.com>, Ori Kam <orika@nvidia.com>
Cc: <matan@nvidia.com>, <rasland@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
<dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] ethdev: fix variable length flow elements support
Date: Wed, 3 Nov 2021 21:04:17 +0000 [thread overview]
Message-ID: <5c9f54cc-8d20-a131-4376-631be940aba3@intel.com> (raw)
In-Reply-To: <20211026090554.9128-1-getelson@nvidia.com>
On 10/26/2021 10:05 AM, Gregory Etelson wrote:
> RTE flow API defines two flow items and actions types - common
> and PMD private. Common RTE flow types are defined in rte_flow.h
> while PMD private types restricted to specific PMD only.
> RTE flow API allows PMD private types in flow rule,
> but it must not try to interpret private item or acton properties.
>
> Current implementation tried to locate PMD private element, item or
> action, in common flow elements records.
>
> The patch restricts access to common flow elements records for
> non-private PMD types only.
>
> Fixes: 6cf72047332b ("ethdev: support flow elements with variable length")
>
> Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> lib/ethdev/rte_flow.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/lib/ethdev/rte_flow.c b/lib/ethdev/rte_flow.c
> index d268784532..a93f68abbc 100644
> --- a/lib/ethdev/rte_flow.c
> +++ b/lib/ethdev/rte_flow.c
> @@ -54,11 +54,13 @@ rte_flow_conv_copy(void *buf, const void *data, const size_t size,
> /**
> * Allow PMD private flow item
> */
> - size_t sz = type >= 0 ? desc[type].size : sizeof(void *);
> + bool rte_type = type >= 0;
> +
> + size_t sz = rte_type ? desc[type].size : sizeof(void *);
> if (buf == NULL || data == NULL)
> return 0;
> rte_memcpy(buf, data, (size > sz ? sz : size));
> - if (desc[type].desc_fn)
Was this (possible) negative array index intentional, or are you fixing it?
> + if (rte_type && desc[type].desc_fn)
> sz += desc[type].desc_fn(size > 0 ? buf : NULL, data);
> return sz;
> }
>
next prev parent reply other threads:[~2021-11-03 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 9:05 Gregory Etelson
2021-11-03 21:04 ` Ferruh Yigit [this message]
2021-11-04 5:33 ` Gregory Etelson
2021-11-04 9:10 ` Ferruh Yigit
2021-11-04 9:20 ` Gregory Etelson
2021-11-04 11:27 ` [dpdk-dev] [PATCH v2] " Gregory Etelson
2021-11-04 12:46 ` Ferruh Yigit
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=5c9f54cc-8d20-a131-4376-631be940aba3@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=thomas@monjalon.net \
--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).