From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Leyi Rong <leyi.rong@intel.com>, <stevex.yang@intel.com>,
<qi.z.zhang@intel.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>
Subject: Re: [PATCH] net/iavf: fix potential out of bounds access
Date: Tue, 8 Mar 2022 15:12:12 +0000 [thread overview]
Message-ID: <80725e8c-74ec-e0d5-56d8-3352140f2e0b@intel.com> (raw)
In-Reply-To: <20220308055617.1465853-1-leyi.rong@intel.com>
On 3/8/2022 5:56 AM, Leyi Rong wrote:
> Fix potential out-out-bounds access as overrunning callee's array of
> size 26 by passing argument rxq->rxdid(which evaluates to 63) in call
> to iavf_rx_scan_hw_ring_flex_rxd.
>
> Coverity issue: 376616
> Fixes: 7b1ba38904a0 ("net/iavf: fix function pointer in multi-process")
> Cc: stable@dpdk.org
>
> Signed-off-by: Leyi Rong <leyi.rong@intel.com>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-03-08 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 5:56 Leyi Rong
2022-03-08 15:12 ` 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=80725e8c-74ec-e0d5-56d8-3352140f2e0b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=leyi.rong@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@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).