From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Cc: dev@dpdk.org, stable@dpdk.org, John Daley <johndale@cisco.com>
Subject: Re: [dpdk-dev] [PATCH] net/enic: fix header sizes when copying flow patterns
Date: Fri, 30 Oct 2020 17:53:15 +0000 [thread overview]
Message-ID: <530c4fb0-8383-8f2e-02d3-dbb8fb758023@intel.com> (raw)
In-Reply-To: <20201030072749.29113-1-hyonkim@cisco.com>
On 10/30/2020 7:27 AM, Hyong Youb Kim wrote:
> Several functions use sizeof(struct rte_flow_item_eth) and
> sizeof(struct rte_flow_item_ipv6) when copying headers. These sizes
> used to coincide with the sizes of rte_ether_hdr and
> rte_ipv6_hdr. But, with recently added fields, rte_flow_item_eth and
> rte_flow_item_ipv6 have grown in size. Use sizeof(rte_ether_hdr) and
> sizeof(rte_ipv6_hdr) instead.
>
> Coverity issue: 363572, 363573
> Fixes: ea7768b5bba8 ("net/enic: add flow implementation based on Flow Manager API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Hyong Youb Kim <hyonkim@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-30 17:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 7:27 Hyong Youb Kim
2020-10-30 17:53 ` Ferruh Yigit [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=530c4fb0-8383-8f2e-02d3-dbb8fb758023@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).