Red Hat Bugzilla – Bug 830356
coverity 12625-12629 - leaks, dead code, unchecked return
Last modified: 2013-02-21 03:18:01 EST
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/353 12629 Resource leak In agmt_set_enabled_from_entry(): Leak of memory or pointers to system resources 12628 Resource leak In agmt_new_from_entry(): Leak of memory or pointers to system resources 12627 Resource leak In memberof_call_foreach_dn(): Leak of memory or pointers to system resources 12626 Logically dead code In cl5CleanRUV(): Code can never be reached because of a logical contradiction 12625 Unchecked return value In trigger_cl_trimming_thread(): Value returned from a function is not checked for errors before being used
please add steps to verify this bug
Passing acceptance tests (mmrepl, memberof) and as long as the latest results from Coverity does not report these defects, we could mark VERIFIED. 1) The latest coverity reports these issues are solved. Plus changing the agreement's status does not occur very often. Thus, the impact is not high. 12629 Resource leak In agmt_set_enabled_from_entry(): Leak of memory or pointers to system resources 12628 Resource leak In agmt_new_from_entry(): Leak of memory or pointers to system resources 2) Extremely narrow possibility to hit the case. Passing memberof acceptance test is good enough. 12627 Resource leak In memberof_call_foreach_dn(): Leak of memory or pointers to system resources 3) No effects on the server's behaviour. 12626 Logically dead code In cl5CleanRUV(): Code can never be reached because of a logical contradiction
4) This case never occurs since trigger_cl_trimming_thread checks the possibility of failure of _cl5AddThread first. Thus, there is no behaviour change. 12625 Unchecked return value In trigger_cl_trimming_thread(): Value returned from a function is not checked for errors before being used
Marking the bug as verified since mmrepl and memberOf acceptance tests PASS 100%.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0503.html