Open krizhanovsky opened 3 years ago
In addition to general-purpose analyzer, kernel has its own set of coccinelle
scripts for checking common kernel-specific mistakes. They could be launched by make coccicheck M=$TEMPESTA_DIR
.
This is seems crucial for the project stability: I reckon this bug https://github.com/tempesta-tech/tempesta/pull/2208/commits/e22a45ddf2782710286f5f427b2b9f99b3f0e417 , which crashed our recent setup, could be found by a static analysis
1526 fixes a dumb bug with signed/unsigned variable. Both the bugs could be found by a static analysis tool, which we run only from time to time due to massive false positives.
The tool integration as a pull request check will make the process less painful since there will be less work on each pull request.
The pull request by the issue must fix all alerts for the current code.
Also consider to compile Tempesta with GCC and/or Clang static analyzers.