Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-7101

SAFE_MUTEX lock order warning when reusing wait_for_commit mutex

        Details

          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.

            Gliffy Diagrams

              Attachments

                Activity

                Hide
                Permalink
                knielsen Kristian Nielsen added a comment -

                Pushed to 10.0.15:

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

                Show
                knielsen Kristian Nielsen added a comment - Pushed to 10.0.15: http://lists.askmonty.org/pipermail/commits/2014-November/006970.html

                  People

                  • Assignee:
                    knielsen Kristian Nielsen
                    Reporter:
                    knielsen Kristian Nielsen
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    1 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: