Raptor3um / raptoreum

MIT License
317 stars 134 forks source link

Quorums lock refactoring #249

Closed CodeIsTheKey closed 1 year ago

CodeIsTheKey commented 1 year ago

cherry-pick of 41190e989958f41350dd63dcb8de2f87ad3255d4: (quorums lock refactoring)

Fix data races triggered by functional tests. (#4247) Function CWallet::KeepKey requires locking as it has concurrent access to database and member nKeysLeftSinceAutoBackup. Avoid data race when reading setInventoryTxToSend size by locking the read. If locking happens after the read, the size may change. Lock cs_mnauth when reading verifiedProRegTxHash. Make fRPCRunning atomic as it can be read/written from different threads simultaneously. Make m_masternode_iqr_connection atomic as it can be read/written from different threads simultaneously. Use a recursive mutex to synchronize concurrent access to quorumVvec. Make m_masternode_connection atomic as it can be read/written from different threads simultaneously. Make m_masternode_probe_connection atomic as it can be read/written from different threads simultaneously. Use a recursive mutex in order to lock access to activeMasterNode. Use a recursive mutex to synchronize concurrent access to skShare. Guarded all mnauth fields of a CNode. Co-authored-by: UdjinM6 UdjinM6@users.noreply.github.com