Date: Tue, 29 Sep 2020 09:31:12 -0700 From: Leonid Shamis <leonid.shamis@...il.com> To: musl@...ts.openwall.com Subject: Robust mutex returning ESRCH We had a bug in our code where a dying process released shared memory (munmap) prior to exit. The process held ownership of a robust mutex within the shared memory, and because the address was unmapped, the robust_list wasn't able to set the appropriate flags. The next attempt to lock the mutex, in another process, returned ESRCH. Should ESRCH be caughtand converted to either a recoverable EOWNERDEAD or ENOTRECOVERABLE? Content of type "text/html" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.