[dpdk-dev] Coverity static code analysis defects in DPDK

[Mcnamara, John]

Hi,

There are currently 50 open Coverity static analysis defects assigned to
the following authors based on "git blame".

Can you please address these defects an close them early in the 18.05
release cycle. Details on what is required are below the list.

    143436  adrien.mazarguil at 6wind.com
    195039  alejandro.lucero at netronome.com
    257034  alejandro.lucero at netronome.com
    140734  arybchenko at solarflare.com
    143450  arybchenko at solarflare.com
    143451  arybchenko at solarflare.com
    158643  changpeng.liu at intel.com
    158654  changpeng.liu at intel.com
    158657  changpeng.liu at intel.com
    158663  changpeng.liu at intel.com
    158658  gaetan.rivet at 6wind.com
    198435  gaetan.rivet at 6wind.com
    198436  gaetan.rivet at 6wind.com
    126444  harish.patil at cavium.com
    126471  harish.patil at cavium.com
    138079  harish.patil at cavium.com
    138087  harish.patil at cavium.com
    144516  harish.patil at cavium.com
    260413  harish.patil at cavium.com
    261777  harish.patil at cavium.com
    261778  harish.patil at cavium.com
    195023  helin.zhang at intel.com
    257029  jasvinder.singh at intel.com
    257007  jerin.jacob at caviumnetworks.com
    257006  matan at mellanox.com
    257010  matan at mellanox.com
    257028  matan at mellanox.com
    257043  matan at mellanox.com<mailto:matan at mellanox.com>
    257040  pascal.mazon at 6wind.com
    158629  radu.nicolau at intel.com
    30688   radu.nicolau at intel.com
    143252  radu.nicolau at intel.com
    143256  radu.nicolau at intel.com
    195022  radu.nicolau at intel.com
    195036  radu.nicolau at intel.com
    143434  remy.horton at intel.com
    127344  reshma.pattan at intel.com
    195040  santosh.shukla at caviumnetworks.com
    195045  santosh.shukla at caviumnetworks.com
    257042  shahafs at mellanox.com
    260412  shahed.shaikh at cavium.com
    260400  shreyansh.jain at nxp.com
    260402  shreyansh.jain at nxp.com
    260403  shreyansh.jain at nxp.com
    260406  shreyansh.jain at nxp.com
    260411  shreyansh.jain at nxp.com
    124563  stephen at networkplumber.org
    158647  thomas at monjalon.net
    140749  vipin.varghese at intel.com
    195021  zhihong.wang at intel.com

You can review the defects online at:

    http://scan.coverity.com/projects/dpdk-data-plane-development-kit

If you aren't registered for the DPDK Coverity you can do so here:

    http://scan.coverity.com/users/sign_up

There are several possible scenarios:

* The defect identified isn't a real issue: In this case you can edit the
  defect online and change the defect "Classification" to "False Positive" or
  "Intentional" and change the "Action" to "Ignore". You should also update
  the "Severity", add yourself as the "Owner" and add a comment note.

* The defect is a real issue: In this case you should submit a patch to fix
  the issues. The patch should include the following information in addition
  to the usual comments and signoff, for example:

    Fixes: dd28bc8c6ef4 ("net/qede: fix VF port creation sequence")
    Coverity issue: 261777

  In Coverity you should update the Classification, Severity, Action (to "Fix
  required" or "Fix Submitted"), Owner and a Comment if necessary.

* The defect wasn't introduced by you. The line where the defect occurs may
  not be the source of the defect. If this is the case then let me know.

John