This issue has been reported in
http://rt.openssl.org/Ticket/Display.html?id=2813 (and fixed).
__
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@op
--On Wednesday, September 05, 2012 12:40 AM +0200 "Dr. Stephen Henson"
wrote:
On Tue, Sep 04, 2012, Quanah Gibson-Mount via RT wrote:
--On Tuesday, September 04, 2012 10:26 PM +0200 Stephen Henson via RT
wrote:
>> [qua...@zimbra.com - Tue Aug 28 22:43:34 2012]:
>>
>> --On Tuesday, August 2
On Tue, Sep 04, 2012, Quanah Gibson-Mount via RT wrote:
> --On Tuesday, September 04, 2012 10:26 PM +0200 Stephen Henson via RT
> wrote:
>
> >> [qua...@zimbra.com - Tue Aug 28 22:43:34 2012]:
> >>
> >> --On Tuesday, August 28, 2012 4:36 PM +0200 The default queue via RT
> >> wrote:
> >>
> >> M
--On Tuesday, September 04, 2012 10:26 PM +0200 Stephen Henson via RT
wrote:
>> [qua...@zimbra.com - Tue Aug 28 22:43:34 2012]:
>>
>> --On Tuesday, August 28, 2012 4:36 PM +0200 The default queue via RT
>> wrote:
>>
>> Mutex information from gdb:
>>
>> (gdb) print mutex
>> $5 = (ldap_pvt_thread
--On Tuesday, September 04, 2012 10:26 PM +0200 Stephen Henson via RT
wrote:
[qua...@zimbra.com - Tue Aug 28 22:43:34 2012]:
--On Tuesday, August 28, 2012 4:36 PM +0200 The default queue via RT
wrote:
Mutex information from gdb:
(gdb) print mutex
$5 = (ldap_pvt_thread_mutex_t *) 0x7f838762
> [qua...@zimbra.com - Tue Aug 28 22:43:34 2012]:
>
> --On Tuesday, August 28, 2012 4:36 PM +0200 The default queue via RT
> wrote:
>
> Mutex information from gdb:
>
> (gdb) print mutex
> $5 = (ldap_pvt_thread_mutex_t *) 0x7f8387626f30
> (gdb) print *mutex
> $6 = {__data = {__lock = 2, __count
In using OpenLDAP 2.4.32 linked to OpenSSL 1.0.1c, OpenSSL can deadlock by
having a thread try to acquire a lock on a mutex that it already owns.
#0 0x7f838666eb53 in epoll_wait () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x004373db in slapd_daemon_task (ptr=0x16cfe48) at daemon.c:25