[PATCH 4/5] Fix deadlock in _int_free consistency check

Wilco Dijkstra Wilco.Dijkstra@arm.com
Thu Oct 12 10:18:00 GMT 2017


Florian Weimer wrote:
    
> I don't think the subject line is correct.  What is the deadlock?  I 
> don't see it.

> -	if (!have_lock
> -	    || ({ __libc_lock_lock (av->mutex);

It's right there. Have_lock means you've just done __libc_lock_lock (av->mutex),
so doing it again (same thread) implies deadlock.

Wilco


More information about the Libc-alpha mailing list