This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/21422] Deadlock in 2.25 pthread_cond_broadcast after process abort
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Tue, 25 Apr 2017 23:41:16 +0000
- Subject: [Bug nptl/21422] Deadlock in 2.25 pthread_cond_broadcast after process abort
- Auto-submitted: auto-generated
- References: <bug-21422-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21422
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #10 from Carlos O'Donell <carlos at redhat dot com> ---
Also note your specific example is not allowed by POSIX. You cannot serialize
the mutex state to disk and reload it. A glibc upgrade could change the
internal structure of the type and the second run of the application would fail
to be able to correctly use the structure. I've written a blog post about the
problems inherent here when background upgrades are allowed:
https://developers.redhat.com/blog/2017/03/13/cc-library-upgrades-and-opaque-data-types-in-process-shared-memory/
--
You are receiving this mail because:
You are on the CC list for the bug.