Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Cause: Configuring the directory server to use Managed Entry and DNA, and running a series of search and update operations to exercise and verify those plugins, while running the directory server using valgrind.
Consequence: valgrind reports memory errors and leaks.
Fix: Make sure memory is used correctly and deleted correctly.
Result: valgrind should report no problems related to Managed Entry and DNA.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/313
1) the ldbm instance dse preop delete callback deletes the entry and dn caches - some other plugins called after this attempt to access those caches
2) normalize_mods2bvals allocs the berval twice in the dn syntax case
3) mep_parse_config_entry allocs value but does not free it
4) dna_be_txn_pre_op can goto bail: in certain cases and attempt to free NULL smods
Comment 2RHEL Program Management
2012-07-10 06:17:50 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 3RHEL Program Management
2012-07-10 23:01:04 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 5Sankar Ramalingam
2013-01-28 17:04:50 UTC
1) setup the directory server to run under valgrind
2) run the managed entry and DNA tests from TET
3) the valgrind output should not report leaks or errors in normalize_mods2bvals(), mep_parse_config_entry(), dna_be_txn_pre_op()
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