From ff2ba49d02dc99b0c3de5712348ae9d588be7ad7 Mon Sep 17 00:00:00 2001 From: Michael Scherer Date: Sun, 19 Feb 2017 11:06:56 +0100 Subject: 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 Reviewed-on: https://review.gluster.org/16668 Smoke: Gluster Build System Tested-by: Nigel Babu NetBSD-regression: NetBSD Build System CentOS-regression: Gluster Build System Reviewed-by: Shyamsundar Ranganathan --- xlators/features/locks/src/common.c | 1 + 1 file changed, 1 insertion(+) (limited to 'xlators/features/locks') diff --git a/xlators/features/locks/src/common.c b/xlators/features/locks/src/common.c index 8cdff0d61ef..68f253d92ad 100644 --- a/xlators/features/locks/src/common.c +++ b/xlators/features/locks/src/common.c @@ -1129,6 +1129,7 @@ pl_does_monkey_want_stuck_lock() long int monkey_unlock_rand = 0; long int monkey_unlock_rand_rem = 0; + /* coverty[DC.WEAK_CRYPTO] */ monkey_unlock_rand = random (); monkey_unlock_rand_rem = monkey_unlock_rand % 100; if (monkey_unlock_rand_rem == 0) -- cgit