From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Xiao Zhang <xiao.zhang@intel.com>, dev@dpdk.org
Cc: qi.z.zhang@intel.com, xiao.w.wang@intel.com,
beilei.xing@intel.com, wenzhuo.lu@intel.com,
qiming.yang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [v2] drivers/net: fix dereference after null check coverity
Date: Tue, 16 Jul 2019 12:55:14 +0100 [thread overview]
Message-ID: <dbf02259-f898-cce7-c64b-99371969ee0b@intel.com> (raw)
In-Reply-To: <1563192937-5825-1-git-send-email-xiao.zhang@intel.com>
On 7/15/2019 1:15 PM, Xiao Zhang wrote:
> This patch tries to fix the coverity issues of dereference after null
> check.
> The addresses of receive queue start segment for ice, avf, i40e,
> fm10k and ixgb were not checked before use. Add check to avoid
> coverity issues.
>
> Coverity issue: 343452
> Coverity issue: 343407
> Fixes: c68a52b8 ("net/ice: support vector SSE in Rx")
> Coverity issue: 343447
> Fixes: 319c421f ("net/avf: enable SSE Rx Tx")
> Coverity issue: 343422
> Coverity issue: 343403
> Fixes: ca74903b ("net/i40e: extract non-x86 specific code from vector driver")
> Coverity issue: 343416
> Fixes: fe65e1e1 ("fm10k: add vector scatter Rx")
> Coverity issue: 13245
> Fixes: 8a44c15a ("net/ixgbe: extract non-x86 specific code from vector driver")
> Cc: stable@dpdk.org
>
> Signed-off-by: Xiao Zhang <xiao.zhang@intel.com>
In patchwork status of this patch is "Superseded" but I can't find the patch
that supersedes this patch, is the current status correct?
next prev parent reply other threads:[~2019-07-16 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-15 12:15 Xiao Zhang
2019-07-16 11:55 ` Ferruh Yigit [this message]
2019-07-16 12:19 ` Zhang, Xiao
2019-07-16 14:26 ` Ferruh Yigit
2019-07-16 14:35 ` Zhang, Xiao
2019-07-16 14:45 ` Ferruh Yigit
2019-07-17 1:47 ` Zhang, Xiao
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=dbf02259-f898-cce7-c64b-99371969ee0b@intel.com \
--to=ferruh.yigit@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=stable@dpdk.org \
--cc=wenzhuo.lu@intel.com \
--cc=xiao.w.wang@intel.com \
--cc=xiao.zhang@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).