The check for mapping tree freed is not threadsafe, and as a result, can cause a crash with an unlocked backend.
<img alt="0001-Ticket-49356-mapping-tree-crash-can-occur-during-tot.patch" src="/389-ds-base/issue/raw/files/e2748604f59eb73141b42a3aca59c7ce5082d9b1e270fa2d4e157b913643db1d-0001-Ticket-49356-mapping-tree-crash-can-occur-during-tot.patch" />
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: None)
commit b851f16 To ssh://git@pagure.io/389-ds-base.git f2b43de..b851f16 master -> master
commit 16916bc To ssh://git@pagure.io/389-ds-base.git 8e17621..16916bc 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
Metadata Update from @firstyear: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1483681
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/2415
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.