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 [email protected]
195039 [email protected]
257034 [email protected]
140734 [email protected]
143450 [email protected]
143451 [email protected]
158643 [email protected]
158654 [email protected]
158657 [email protected]
158663 [email protected]
158658 [email protected]
198435 [email protected]
198436 [email protected]
126444 [email protected]
126471 [email protected]
138079 [email protected]
138087 [email protected]
144516 [email protected]
260413 [email protected]
261777 [email protected]
261778 [email protected]
195023 [email protected]
257029 [email protected]
257007 [email protected]
257006 [email protected]
257010 [email protected]
257028 [email protected]
257043 [email protected]<mailto:[email protected]>
257040 [email protected]
158629 [email protected]
30688 [email protected]
143252 [email protected]
143256 [email protected]
195022 [email protected]
195036 [email protected]
143434 [email protected]
127344 [email protected]
195040 [email protected]
195045 [email protected]
257042 [email protected]
260412 [email protected]
260400 [email protected]
260402 [email protected]
260403 [email protected]
260406 [email protected]
260411 [email protected]
124563 [email protected]
158647 [email protected]
140749 [email protected]
195021 [email protected]
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
