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

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