Version: 1.3.0 Is this version info correct? (I guess it could be 1.3.2/master?)
Replying to [comment:2 nhosoi]:
Yes this is with 1.3.2(master).
In ldbm_back_delete() I also forced the setting of the error code in case any future code shuffling occurs.
in ldbm_delete - in the first 3 cases, retval = -1 already - it is not necessary to set it, except perhaps to make the assumptions more clear
in ldbm_modrdn - would rather not make a change that is only formatting
revision 0001-Ticket-47449-deadlock-after-adding-and-deleting-entr.patch
Replying to [comment:6 rmeggins]:
Right, I was under the assumption that this bug might have happened from code being shuffled around. So I hard set it to avoid future mistakes. But this "mistake" is present in all versions of 389(at least 1.2.11 and up). Anyway I just remove it.
in ldbm_modrdn - would rather not make a change that is only formatting.
No problem, it was only formatting.
New patch attached.
git merge ticket47449 Updating aa55789..6bd78b3 Fast-forward ldap/servers/slapd/back-ldbm/ldbm_delete.c | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-)
git push origin master To ssh://git.fedorahosted.org/git/389/ds.git aa55789..6bd78b3 master -> master
commit 6bd78b3
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=988559
1.3.1
024abee..8ea067b 389-ds-base-1.3.1 -> 389-ds-base-1.3.1
1.3.0
3f75400..93bde65 389-ds-base-1.3.0 -> 389-ds-base-1.3.0
1.2.11
c1dcfc6..66fbebc 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 66fbebc
Metadata Update from @nkinder: - Issue assigned to mreynolds - Issue set to the milestone: 1.2.11.22
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/786
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.