So we are finding these race conditions (leading to heap-use-after-free)
when you stop the server while an import task is running. The current
code aborts the task which leaves the database unusable until it is
fully reinitialized at a later time. Unfortunately the code that
handles this is complex, and very error prone.
I'd like to allow the import task to complete before fully shutting the
server down. Code fix is trivial, but do we want the import to finish,
or should the import be aborted (and database left broken)? Thoughts?
Opinions?
Thanks,
Mark
--
389 Directory Server Development Team
_______________________________________________
389-devel mailing list -- 389-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-devel@xxxxxxxxxxxxxxxxxxxxxxx
