#47817 The error result text message should be obtained just prior to sending result
Closed: wontfix None Opened 8 years ago by mreynolds.

Its possible that backend plugins can set the error text, which frees the existing result text(if any). The problem is that in the backend we grab a pointer to the result text before we call the backend postop plugins. If a plugin sets the result text we will get invalid read errors reported by valgrind.

git merge ticket47817
Updating f2eb45b..68e7668
ldap/servers/slapd/back-ldbm/ldbm_add.c | 6 ++++--
ldap/servers/slapd/back-ldbm/ldbm_delete.c | 3 ++-
ldap/servers/slapd/back-ldbm/ldbm_modify.c | 1 +
ldap/servers/slapd/back-ldbm/ldbm_modrdn.c | 1 +
4 files changed, 8 insertions(+), 3 deletions(-)

git push origin master
f2eb45b..68e7668 master -> master

commit 68e7668
Author: Mark Reynolds mreynolds@redhat.com
Date: Tue Jun 17 17:58:54 2014 -0400

887a72e..dd51540 389-ds-base-1.3.2 -> 389-ds-base-1.3.2
commit dd51540

98b0853..e6762cb 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
commit e6762cb8cd43d8753f64f00cb3da36dc817d3c5d

d8f6af4..6f6142e 389-ds-base-1.2.11 -> 389-ds-base-1.2.11
commit 6f6142e

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone:

6 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/1148

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)

2 years ago

Login to comment on this ticket.