DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wenzhuo Lu <wenzhuo.lu@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/ice: fix coverity issues
Date: Tue, 23 Apr 2019 11:40:00 +0100	[thread overview]
Message-ID: <dbbb1840-5a87-49ee-0570-72f471c9eed5@intel.com> (raw)
Message-ID: <20190423104000.nl5EiGeHMVyuxj9rgWyvUjOfm95ux11eNLMPPQQIo2s@z> (raw)
In-Reply-To: <1555551081-29524-1-git-send-email-wenzhuo.lu@intel.com>

On 4/18/2019 2:31 AM, Wenzhuo Lu wrote:
> Fix the issues reported by Coverity check, "Null-checking
> vsi suggests that it may be null, but it has already been
> dereferenced on all paths leading to the check."

Hi Wenzhuo,

Can you please list the coverity issues addressed, the format we have is:
Coverity issue: ####

Also the patch title doesn't say much, can you please put what exactly fixed,
"fix possible null pointer dereference" ?


> 
> Fixes: e0dcf94a0d7f ("net/ice: support VLAN ops")
> Fixes: ff963bfa7cb1 ("net/ice: support RSS")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>

<...>


  parent reply	other threads:[~2019-04-23 10:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-18  1:31 Wenzhuo Lu
2019-04-18  1:31 ` Wenzhuo Lu
2019-04-22  6:57 ` Yang, Qiming
2019-04-22  6:57   ` Yang, Qiming
2019-04-22  7:14   ` Rami Rosen
2019-04-22  7:14     ` Rami Rosen
2019-04-23  3:29   ` Zhang, Qi Z
2019-04-23  3:29     ` Zhang, Qi Z
2019-04-23 10:40 ` Ferruh Yigit [this message]
2019-04-23 10:40   ` Ferruh Yigit
2019-04-24  2:15   ` Lu, Wenzhuo
2019-04-24  2:15     ` Lu, Wenzhuo
2019-04-24  2:43 ` [dpdk-dev] [PATCH v2] net/ice: fix possible null pointer dereference Wenzhuo Lu
2019-04-24  2:43   ` Wenzhuo Lu
2019-04-24 15:56   ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2019-04-24 15:56     ` 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=dbbb1840-5a87-49ee-0570-72f471c9eed5@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=wenzhuo.lu@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).