[MDEV-7101] SAFE_MUTEX lock order warning when reusing wait_for_commit mutex Created: 2014-11-13  Updated: 2014-11-13  Resolved: 2014-11-13

Status: Closed
Project: MariaDB Server
Component/s: Replication
Affects Version/s: 10.0.14
Fix Version/s: 10.0.15

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: parallelslave, replication


 Description   

The wait_for_commit mutex is reused by parallel replication for transactions
that are completely unrelated (as part of the rpl_group_info freelist).

This can cause SAFE_MUTEX to give false warnings about incorrect locking
orders, where first M1 is taken while M2 is held, and later M2 is taken while
M1 is held.

The fix should be to reset the mutex when it is reused for a new purpose, in
SAFE_MUTEX builds.

 Comments   
Comment by Kristian Nielsen [ 2014-11-13 ]

Pushed to 10.0.15:

http://lists.askmonty.org/pipermail/commits/2014-November/006970.html

Generated at Thu Feb 08 07:17:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.