[Bug libc/770] possible deadlock on double-free logging

["bugzilla at tree dot tlrmx dot org" <sourceware-bugzilla at sourceware dot org>]

------- Additional Comments From bugzilla at tree dot tlrmx dot org  2008-04-30 20:27 -------
This happens to us once a day or so (obviously the double-free that causes the
problem is periodic in some fashion). For us deadlocking is mostly worse than
just allowing some potential corruption due to a double-free.

We are using glibc-2.5-12 x86-64 on a CentOS 5 machine.

Here are some musings from #glibc IRC where I reported that I had seen this bug.

<ryanarn> hrm.. that one's been about for a while.  I wonder why there's been no
movement on it.
<sjmunroe> the mutex it locked in free which calls _int_free(), so _int_free
does not know about the lock
<sjmunroe> to avoid this _int_free would have to report the error back to free
so free could do the unlock before reposting the error


-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugzilla at tree dot tlrmx
                   |                            |dot org


http://sourceware.org/bugzilla/show_bug.cgi?id=770

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.