[PATCH 4/6] Do not call _xend if no transaction is active.

Dominik Vogt vogt@linux.vnet.ibm.com
Mon Sep 2 08:05:00 GMT 2013


If pthread_mutex_unlock is called without the futex locked and no transaction
open does not necessarily mean that pthread_mutex_lock has not been called.
The transaction may have been closed in third party code.  While this _may_ be
a bug in the software as a whole, unlock should not crash the program.

Overall it is problematic to close transactions if you are not completely sure
that you have opened the transaction yourself.  I see no general solution for
this except installing coding rules for transactional code.

Fix a whitespace error as a side effect.

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt
IBM Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0004-x86-Do-not-call-_xend-if-no-transaction-is-active.patch
Type: text/x-diff
Size: 1253 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20130902/c4d6197b/attachment.bin>


More information about the Libc-alpha mailing list