https://bugs.openldap.org/show_bug.cgi?id=9930
--- Comment #2 from Ondřej Kuzník <[email protected]> --- Thread 5 has paused the server and is now waiting to wlock() olcDatabase={1}mdb,cn=config config entry, but thread 6 already has read lock on it (and is currently waiting for the pause to end). The issue is that workers are not meant to join the pause while holding the rlock but slap_send_search_entry->send_ldap_ber is willing to do just that because we got EAGAIN/EWOULDBLOCK on the socket. I assume this can end up worse than a deadlock if the server actually reconfigured itself while we were waiting for the writer to flush? -- You are receiving this mail because: You are on the CC list for the issue.
