Red Hat Bugzilla – Bug 458507
Memory leak setting new password storage scheme
Last modified: 2015-01-04 18:33:39 EST
In config_set_pw_storagescheme, new_schema is allocated in both the non apply and the apply case, but it is only freed in the apply case.
Created attachment 313858 [details]
> but it is only freed in the apply case.
Rather, consumed, isn't it? ;)
slapdFrontendConfig->pw_storagescheme = new_scheme;
This bug can only be reproduced by an admin user changing the password storage scheme, not an anonymous user. You have to authenticate then have special privileges.
Created attachment 314145 [details]
cvs commit log - DS8.0
Reviewed by: nkinder (Thanks!)
Fix Description: In config_set_pw_storagescheme, new_schema is allocated in both the non apply
and the apply case, but it is only freed in the apply case. The solution is to free it in the non apply case.
Platforms tested: RHEL5, Fedora 8
Flag Day: no
Doc impact: no
QA impact: should be covered by regular nightly and manual testing
New Tests integrated into TET: none
How can QE verify this? What to look for in the valgrind output?
(In reply to comment #8)
> How can QE verify this? What to look for in the valgrind output?
Look for a memory leak in config_set_pw_storagescheme in the valgrind output.
verified 8.0 RHEL4-32, RHEL4-64, RHEL5-32, RHEL5-64
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Created attachment 315145 [details]
cvs commit log - HEAD