Detect inconsistent lock ordering

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.1.7
    • Component/s: Concurrency
    • None
    • Storage Execution
    • QuInt B (11/02/15)
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In order to avoid potential deadlocks, we require consistent ordering of lock acquisition/release. Currently there are no checks for these, and it is easy to accidentally introduce incorrect orderings. Moreover, there is a possibility that some of these can be extremely rare, potentially leading to deadlock.

      By checking lock ordering in debug builds, we can reduce the likelihood of such problems.

              Assignee:
              [DO NOT USE] Backlog - Storage Execution Team
              Reporter:
              Geert Bosch
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: