Skip to content

Conversation

brghash
Copy link
Contributor

@brghash brghash commented Oct 1, 2025

Summary of changes

  • Replaced the dangerous lock algorithm in HDRF with a safer backoff algorithm
  • Introudced owns_lock member variable to Record class to stop the unlocking of unowned mutexes

Why

  • The recursive call of the lock algorithm of HDRF is potentially dangerous
  • The unlocking of unowned mutexes was caused by the releaseLock() function, as there was no check to see it was owned or not

Related issue

… with a safer backoff one. Stop the unlocking of unowned mutexes with the implementation of the owns_lock member variable.
@ZigRazor ZigRazor merged commit ebed856 into ZigRazor:master Oct 2, 2025
10 of 17 checks passed
@brghash brghash deleted the update branch October 2, 2025 18:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PartitionTest.test_2 fails 50% of the time due to "unlock of unowned mutex" - MSVC
2 participants