[Bug nptl/13690] pthread_mutex_unlock potentially cause invalid access

["lopresti at gmail dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=13690

Pat <lopresti at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lopresti at gmail dot com

--- Comment #27 from Pat <lopresti at gmail dot com> ---
If you have to wait for all calls to mutex_unlock to return before you can
destroy the mutex, how are you supposed to guarantee that, exactly?

You can only do so by synchronizing the threads in some other way. So every
mutex has to be guarded by another mutex which has to be guarded by another
mutex...

...except for the last mutex, which is global or static or whatever and never
gets destroyed. Problem solved!

Seriously, think about the kind of code you would have to write to deal with
these semantics. Is that what you think POSIX wanted to put people through
(despite the actual example they give)? Is that what glibc wants to put people
through?

You do not need "clarification" from anybody to recognize that these are
serious bugs. The only interesting question is how many years it's going to
take.

-- 
You are receiving this mail because:
You are on the CC list for the bug.