https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c0 Summary: pthread_mutex_trylock violates POSIX semantics on systems with lock elision Classification: openSUSE Product: openSUSE 13.1 Version: Final Platform: x86-64 OS/Version: openSUSE 13.1 Status: NEW Severity: Critical Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: jmattson@vmware.com QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 On Intel Haswell systems, pthread_mutex_trylock violates POSIX semantics. It fails to return EBUSY when the mutex is in the locked state. This breaks existing software that expects POSIX semantics and links dynamically with libc on openSUSE 13.1. Reproducible: Always Steps to Reproduce: 1. Put a mutex into the locked state with pthread_mutex_lock. 2. Query the state of the mutex with pthread_mutex_trylock. Actual Results: pthread_mutex_trylock returns 0. Expected Results: pthread_mutex_trylock should return EBUSY. See https://www.sourceware.org/ml/libc-alpha/2012-12/msg00398.html. Andi Kleen writes:
I would claim to be at least covered by the rationale, but ok. Too bad it's a shall.
Can you point me to any real software impacted by this?
VMware Workstation and Player are real software packages that are impacted by this decision. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.