https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c1 Christian Prause changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cprause@suse.com --- Comment #1 from Christian Prause 2014-02-27 12:15:08 UTC --- Hi, I am getting ../nptl/pthread_mutex_lock.c:80: __pthread_mutex_cond_lock: Assertion `mutex->__data.__owner == 0' failed. with Inkscape (just while starting) on a Haswell (i7-4770) box same thing? Cheers Chris -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c Marcus Meissner changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |meissner@suse.com AssignedTo|bnc-team-screening@forge.pr |schwab@suse.com |ovo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c4 --- Comment #4 from Michael Matz 2014-03-03 14:32:08 UTC --- FWIW, this trivial testcase that checks exactly what is described in the initial comment does _not_ fail: --------------------------------------------------------------- #include #include #include #include int main() { pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER; if (pthread_mutex_lock (&mutex)) error (1, errno, "mutex lock failed"); if (pthread_mutex_trylock (&mutex) != 0) printf ("Okay\n"); else error (1, errno, "trylock didn't fail with EBUSY"); return 0; } --------------------------------------------------------------- Tried on haswell and non-haswell, on haswell with HLE routines, e.g. with glibc-2.18.90-4.24.x86_64 . So yes, this needs a different self-contained testcase. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c19 Jim Mattson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jmattson@vmware.com | --- Comment #19 from Jim Mattson 2014-03-03 18:36:55 UTC --- I misinterpreted what I was seeing, and I jumped to the wrong conclusion. The actual problem is that a successful trylock followed by an unlock reduces __nusers below 0. Here's a sample: #include #include #include #include pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER; void lockN(int n) { int i; for (i = 0; i < n; i++) { if (pthread_mutex_trylock (&mutex) == 0) { pthread_mutex_unlock (&mutex); } } } int main() { int rc; lockN(5); if ((rc = pthread_mutex_destroy(&mutex)) != 0) { error(1, errno, "pthread_mutex_destroy failed with %d", rc); } } Run on pre-Haswell systems, this program succeeds. Run on Haswell systems, it fails as follows: /foo: pthread_mutex_destroy failed with 16 On a Haswell system, we can see that __nusers has gone negative: Breakpoint 1, main () at foo.c:22 22 if ((rc = pthread_mutex_destroy(&mutex)) != 0) { (gdb) p mutex $1 = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 4294967291, __kind = 0, __spins = 196608, __list = {__prev = 0x0, __next = 0x0}}, __size = '\000' , "\373\377\377\377\000\000\000\000\000\000\003", '\000' , __align = 0} (gdb) p (int)4294967291 $2 = -5 Pre-Haswell, __nusers is 0, as expected: Breakpoint 1, main () at foo.c:22 22 if ((rc = pthread_mutex_destroy(&mutex)) != 0) { (gdb) p mutex $1 = {__data = {__lock = 0, __count = 0, __owner = 0, __nusers = 0, __kind = 0, __spins = 0, __list = { __prev = 0x0, __next = 0x0}}, __size = '\000' , __align = 0} -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c21 --- Comment #21 from Andreas Schwab 2014-03-04 10:09:11 CET --- Forwarded to https://sourceware.org/bugzilla/show_bug.cgi?id=16657 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c23 Jim Mattson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jmattson@vmware.com | --- Comment #23 from Jim Mattson 2014-03-05 13:01:57 UTC --- pthread_mutex_destroy does not seem to think this is okay: int __pthread_mutex_destroy (mutex) pthread_mutex_t *mutex; { LIBC_PROBE (mutex_destroy, 1, mutex); if ((mutex->__data.__kind & PTHREAD_MUTEX_ROBUST_NORMAL_NP) == 0 && mutex->__data.__nusers != 0) return EBUSY; /* Set to an invalid value. */ mutex->__data.__kind = -1; return 0; } After successfully using pthread_mutex_trylock to lock the mutex and subsequently using pthread_mutex_unlock to unlock the mutex, pthread_mutex_destroy fails with EBUSY. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c25 Jim Mattson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jmattson@vmware.com | --- Comment #25 from Jim Mattson 2014-03-05 13:13:46 UTC --- Perhaps I was mistaken and the error is with pthread_mutex_destroy rather than pthread_mutex_trylock. In any event, the combination of the two violates POSIX semantics. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c26 Andreas Schwab changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |jmattson@vmware.com --- Comment #26 from Andreas Schwab 2014-03-05 14:25:08 CET --- What happens if you ignore the error? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c28 --- Comment #28 from Andreas Schwab 2014-03-05 15:03:00 CET --- What happens if you ignore the error? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c30 Jim Mattson changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|jmattson@vmware.com | --- Comment #30 from Jim Mattson 2014-03-05 14:41:45 UTC --- What happens if pthread_mutex_destroy always returns 0? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c32 --- Comment #32 from Pieter Hollants 2014-03-11 16:23:09 UTC --- Created an attachment (id=581713) --> (http://bugzilla.novell.com/attachment.cgi?id=581713) Backtrace of inkscape crashing with pthread elision left enabled I can not see most of the comments in this ticket, so I don't know what you guys have already done before, but for what it's worth: the related ticket #867168 for SLES12 requested a backtrace for inkscape which I'll add tomorrow, but here's the same backtrace for openSUSE 13.1. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c34 --- Comment #34 from Pieter Hollants 2014-03-11 16:59:23 UTC --- Created an attachment (id=581719) --> (http://bugzilla.novell.com/attachment.cgi?id=581719) valgrind --tool=drd run of inkscape As requested, the output of "valgrind --tool=drd" running our inkscape job. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c36 --- Comment #36 from Bernhard Wiedemann 2014-03-31 18:00:14 CEST --- This is an autogenerated message for OBS integration: This bug (865968) was mentioned in https://build.opensuse.org/request/show/228350 Factory / glibc -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c41 --- Comment #41 from Christian Prause 2014-04-30 09:51:11 UTC --- Andreas I installed your test Version of glibc on 13.1 and was not able to reproduce the inkscape crash since. Will this be pushed to 13.1 updates? cheers Chris -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c43 --- Comment #43 from Benjamin Brunner 2014-05-07 15:05:51 CEST --- @Andreas, thanks for your submission. I started an update for openSUSE 13.1. @Christian, the update will probably be available mid of next week, if you need it earlier, you can also use the packages from http://download.opensuse.org/repositories/openSUSE:/Maintenance:/2793/openSU... as soon as it's build. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=865968 https://bugzilla.novell.com/show_bug.cgi?id=865968#c45 --- Comment #45 from Swamp Workflow Management 2014-05-15 13:04:26 UTC --- openSUSE-RU-2014:0649-1: An update that has one recommended fix can now be installed. Category: recommended (low) Bug References: 865968 CVE References: Sources used: openSUSE 13.1 (src): glibc-2.18-4.15.1, glibc-testsuite-2.18-4.15.3, glibc-utils-2.18-4.15.2 -- 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.