From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/ice: fix coverity issues
Date: Wed, 24 Apr 2019 02:15:46 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909407FF7A9@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <dbbb1840-5a87-49ee-0570-72f471c9eed5@intel.com>
Hi Ferruh,
> -----Original Message-----
> From: Yigit, Ferruh
> Sent: Tuesday, April 23, 2019 6:40 PM
> To: Lu, Wenzhuo <wenzhuo.lu@intel.com>; dev@dpdk.org
> Cc: stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] net/ice: fix coverity issues
>
> 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" ?
Thanks for the comments. Will send V2.
next prev parent reply other threads:[~2019-04-24 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 1:31 [dpdk-stable] " Wenzhuo Lu
2019-04-22 6:57 ` [dpdk-stable] [dpdk-dev] " Yang, Qiming
2019-04-22 7:14 ` Rami Rosen
2019-04-23 3:29 ` Zhang, Qi Z
2019-04-23 10:40 ` Ferruh Yigit
2019-04-24 2:15 ` Lu, Wenzhuo [this message]
2019-04-24 2:43 ` [dpdk-stable] [PATCH v2] net/ice: fix possible null pointer dereference Wenzhuo Lu
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=6A0DE07E22DDAD4C9103DF62FEBC0909407FF7A9@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).