-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
3
-
9223372036854775807
I've been experimenting with more static analyzers (Coverity in this case). While it does have some false positives, it looks like it found a number of legitimate bugs. See https://scan.coverity.com/projects/lustre for details.
It's seems like Coverity has been used with Lustre in the past (see: https://wiki.lustre.org/images/8/8a/LUG2013-Lustre_Static_Code_Analysis-Bull.pdf). Although, it doesn't seem like it's been run in a while.
Also, there's a number of Coverity comments that seem out-dated and should probably just be cleaned up.
- is related to
-
LU-18560 ldiskfs_write_ldd(): Coverity reports issues
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- is related to
-
LU-1855
Coverity: Fix 'out-of-bounds access' errors
-
- Resolved
-
-
LU-1856
Coverity: Fix 'Out-of-bounds write' errors
-
- Resolved
-
-
LU-1884
Coverity: Fix 'resource leak' errors
-
- Resolved
-
-
LU-1857
Coverity: Fix 'Unbounded source buffer' errors
-
- Resolved
-
-
LU-1889
Fix false 'uninitialized scalar variable' errors found by Coverity
-
- Resolved
-
-
LU-1907
Remove function resolution mistakes made by Coverity
-
- Resolved
-
-
LU-2709
Coverity: Fix 'memory corruption' errors
-
- Resolved
-
-
LU-2710
Remove function resolution mistakes made by Coverity
-
- Resolved
-