http://bugzilla.suse.com/show_bug.cgi?id=917810
Leonardo Chiquitto changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |IN_PROGRESS
CC| |schwab@suse.com
Flags| |needinfo?(schwab@suse.com)
--- Comment #4 from Leonardo Chiquitto ---
It's trying to unlock a mutex that's not locked. pthread_mutex_unlock() returns
error and automount aborts.
Unlocking an unlocked mutex has either "undefined behavior" or "error returned"
according to the man page.
Looks like in most systems, "undefined behavior" translates to "return
success". The code below works fine on my machine
(kernel-desktop-3.18.3-1.3.x86_64, glibc-2.20-2.2.x86_64), on 11-SP3
(kernel-default-3.0.101-0.46.1, glibc-2.11.3-17.80.3) but segfaults on oldboy
(kernel-default-3.14.0-2.2.x86_64,
glibc-2.19-19.1.x86_64).
#include
int main(void)
{
pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
pthread_mutex_lock(&mutex);
pthread_mutex_unlock(&mutex);
return pthread_mutex_unlock(&mutex);
}
Andreas, do you remember if the behavior changed sometime ago?
--
You are receiving this mail because:
You are on the CC list for the bug.