All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Xiao Zhang <xiao.zhang@intel.com>
Cc: dev@dpdk.org, qiming.yang@intel.com, beilei.xing@intel.com,
	stable@dpdk.org
Subject: Re: [dpdk-dev] [v2 0/5] fix dereference after null check coverity
Date: Mon, 5 Aug 2019 23:46:27 +0800	[thread overview]
Message-ID: <20190805154627.GA66560@intel.com> (raw)
In-Reply-To: <1565047254-66826-1-git-send-email-xiao.zhang@intel.com>

On 08/06, Xiao Zhang wrote:
>This patch tries to fix (dereference after null check) coverity issue.
>The address of first segmented packets for ice, iavf, i40e fm10k and ixgbe
>was not set correctly during reassembling packets which led to this issue.
>
>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
>
>v2 Add cover letter and move the fix after invalidation check
>
>Xiao Zhang (5):
>  net/ixgbe: fix dereference after null check coverity
>  net/ice: fix dereference after null check coverity
>  net/i40e: fix dereference after null check coverity
>  net/iavf: fix dereference after null check coverity
>  net/fm10k: fix dereference after null check coverity
>
> drivers/net/fm10k/fm10k_rxtx_vec.c     | 1 +
> drivers/net/i40e/i40e_rxtx_vec_avx2.c  | 1 +
> drivers/net/i40e/i40e_rxtx_vec_sse.c   | 1 +
> drivers/net/iavf/iavf_rxtx_vec_sse.c   | 1 +
> drivers/net/ice/ice_rxtx_vec_avx2.c    | 1 +
> drivers/net/ice/ice_rxtx_vec_sse.c     | 1 +
> drivers/net/ixgbe/ixgbe_rxtx_vec_sse.c | 1 +
> 7 files changed, 7 insertions(+)
>
>-- 
>2.7.4
>

For the series:
Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>

  reply	other threads:[~2019-08-05 15:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-04 21:00 [dpdk-dev] [PATCH 1/5] net/fm10k: fix dereference after null check coverity Xiao Zhang
2019-08-04 21:00 ` [dpdk-dev] [PATCH 2/5] net/iavf: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-dev] [PATCH 3/5] net/i40e: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-dev] [PATCH 4/5] net/ice: " Xiao Zhang
2019-08-04 21:00 ` [dpdk-dev] [PATCH 5/5] net/ixgbe: " Xiao Zhang
2019-08-05  3:35 ` [dpdk-dev] [PATCH 1/5] net/fm10k: " Ye Xiaolong
2019-08-05 23:20 ` [dpdk-dev] [v2 0/5] " Xiao Zhang
2019-08-05 15:46   ` Ye Xiaolong [this message]
2019-08-06 11:30     ` Zhang, Qi Z
2019-08-06 14:01       ` Ye Xiaolong
2019-08-06 14:13         ` Zhang, Xiao
2019-08-05 23:20   ` [dpdk-dev] [PATCH v2 1/5] net/ixgbe: " Xiao Zhang
2019-08-05 23:20   ` [dpdk-dev] [PATCH v2 2/5] net/ice: " Xiao Zhang
2019-08-05 23:20   ` [dpdk-dev] [PATCH v2 3/5] net/i40e: " Xiao Zhang
2019-08-05 23:20   ` [dpdk-dev] [PATCH v2 4/5] net/iavf: " Xiao Zhang
2019-08-05 23:20   ` [dpdk-dev] [PATCH v2 5/5] net/fm10k: " Xiao Zhang

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=20190805154627.GA66560@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.