Description of problem: Coverty scan return false positive regarding crypto, since there is code using random. However taht's either dht code, or code that generate errors, and none is crypto related (nor critical). So random is fine, and in order to make coverty scan report useful, would like to filter them. I am not 100% sure of the syntax, but that's the one documented around. If someone can confirm the syntax, please do not hesitate :) Version-Release number of selected component (if applicable): git head How reproducible: each time Steps to Reproduce: 1. read coverty scan report Actual results: false positives Expected results: less false positives Additional info:
REVIEW: https://review.gluster.org/16668 (Filter coverty false positives) posted (#1) for review on master by Michael Scherer (misc)
COMMIT: https://review.gluster.org/16668 committed in master by Shyamsundar Ranganathan (srangana) ------ commit ff2ba49d02dc99b0c3de5712348ae9d588be7ad7 Author: Michael Scherer <misc> Date: Sun Feb 19 11:06:56 2017 +0100 Filter coverty false positives Since random is not used for anything cryptographically related, it is fine to use it in those instances. Change-Id: I720172285f60d6bc477c7169c7286fc018ebdf8f BUG: 1424764 Signed-off-by: Michael Scherer <misc> Reviewed-on: https://review.gluster.org/16668 Smoke: Gluster Build System <jenkins.org> Tested-by: Nigel Babu <nigelb> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.11.0, please open a new bug report. glusterfs-3.11.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/