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.mazarg...@6wind.com
195039 alejandro.luc...@netronome.com
257034 alejandro.luc...@netronome.com
140734 arybche...@solarflare.com
143450 arybche...@solarflare.com
143451 arybche...@solarflare.com
158643 changpeng....@intel.com
158654 changpeng....@intel.com
158657 changpeng....@intel.com
158663 changpeng....@intel.com
158658 gaetan.ri...@6wind.com
198435 gaetan.ri...@6wind.com
198436 gaetan.ri...@6wind.com
126444 harish.pa...@cavium.com
126471 harish.pa...@cavium.com
138079 harish.pa...@cavium.com
138087 harish.pa...@cavium.com
144516 harish.pa...@cavium.com
260413 harish.pa...@cavium.com
261777 harish.pa...@cavium.com
261778 harish.pa...@cavium.com
195023 helin.zh...@intel.com
257029 jasvinder.si...@intel.com
257007 jerin.ja...@caviumnetworks.com
257006 ma...@mellanox.com
257010 ma...@mellanox.com
257028 ma...@mellanox.com
257043 ma...@mellanox.com<mailto:ma...@mellanox.com>
257040 pascal.ma...@6wind.com
158629 radu.nico...@intel.com
30688 radu.nico...@intel.com
143252 radu.nico...@intel.com
143256 radu.nico...@intel.com
195022 radu.nico...@intel.com
195036 radu.nico...@intel.com
143434 remy.hor...@intel.com
127344 reshma.pat...@intel.com
195040 santosh.shu...@caviumnetworks.com
195045 santosh.shu...@caviumnetworks.com
257042 shah...@mellanox.com
260412 shahed.sha...@cavium.com
260400 shreyansh.j...@nxp.com
260402 shreyansh.j...@nxp.com
260403 shreyansh.j...@nxp.com
260406 shreyansh.j...@nxp.com
260411 shreyansh.j...@nxp.com
124563 step...@networkplumber.org
158647 tho...@monjalon.net
140749 vipin.vargh...@intel.com
195021 zhihong.w...@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
