indmanager: Forcefully recreate mutexes on indication stop

Creating mutexes with the PTHREAD_MUTEX_ERRORCHECK attribute proved to be
a wrong way. It turned out locking was not working properly as any attempt
to lock already locked mutex failed with a return value that we didn't check.
The only reason we were using this special attribute was to prevent crash on
forcefully unlocking mutex in an unknown state. That didn't work either as long
as EPERM was returned when trying to unlock the mutex that has been locked from
other thread... that was forcefully canceled. That only led to deadlocks
fortunately hard to hit, unfortunately equally hard to debug.

0 files changed, 0 insertions, 0 deletions