#313 valgrind reported memleaks and mem errors
Closed: wontfix None Opened 9 years ago by rmeggins.

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


0004-destroy-the-entry-cache-and-dn-cache-in-the-dse-post.patch
0004-destroy-the-entry-cache-and-dn-cache-in-the-dse-post.patch

To ssh://git.fedorahosted.org/git/389/ds.git
e2532d8..93adf5f master -> master
commit changeset:93adf5f/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Thu Mar 1 19:27:09 2012 -0700

destroy the entry cache and dn cache in the dse post op delete callback

don't destroy the entry and dn cache in the ldbm instance pre op delete
callback because other preop callback may attempt to access the
caches - wait and destroy it in the dse post op delete callback
Reviewed by: nhosoi (Thanks!)

commit changeset:f6e4d3d/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Thu Mar 1 18:50:05 2012 -0700

memleak in normalize_mods2bvals

do not re malloc the berval again - only need to do it once
Reviewed by: nhosoi (Thanks!)

commit changeset:54fbe0b/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Thu Mar 1 18:47:34 2012 -0700

memleak in mep_parse_config_entry

pass in value to slapi_sdn_new_dn_passin() so that entry->template_sdn
will own the memory
Reviewed by: nhosoi (Thanks!)

commit changeset:afd6b1f/389-ds-base
Author: Rich Megginson rmeggins@redhat.com
Date: Wed Feb 29 17:27:32 2012 -0700

handle null smods

Under certain error conditions, smods will be NULL at the end of the function.
Do not call passout if smods is NULL.
Reviewed by: nhosoi (Thanks!)

Added initial screened field value.

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: 1.2.11.a1

4 years ago

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/313

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

9 months ago

Login to comment on this ticket.

Metadata