forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
refactor: drop fMasternodeMode global, create new context for masternode mode-only logic (ActiveContext), move spun-off signers and EHF signals handler
#6828
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
562ad2b
wallet: drop collateral outpoints filtering from balance calculation
kwvg be84075
refactor: drop `fMasternodeMode` global
kwvg 314f070
refactor: move InstantSend signer to new `ActiveContext`
kwvg fcabb3d
refactor: move ChainLock signer to `ActiveContext`
kwvg afec9ae
refactor: move CoinJoin server to `ActiveContext`
kwvg d52795c
refactor: clean up `CCoinJoinServer`, remove redundant checks
kwvg 83707a0
refactor: create notification interface for masternode mode
kwvg ecb924c
refactor: move EHF signals handler to `ActiveContext`
kwvg f4ac71c
lint: update circular dependencies allowlist, minor cleanup
kwvg File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🛠️ Refactor suggestion
Make signer pointer updates thread-safe (guard with cs).
m_signer is mutated at runtime via Connect/Disconnect while CChainLocksHandler runs a scheduler thread. Without synchronization, this is a data race. Guard the pointer with cs and lock in ConnectSigner/DisconnectSigner.
Apply this minimal diff:
📝 Committable suggestion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bot, please confirm we could just use an atomic here right? as we are just guarding for the writing to the pointer
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@PastaPastaPasta Yes, you're absolutely correct! Using
std::atomic<chainlock::ChainLockSigner*>would be the better approach here since we're only guarding pointer read/write operations.The access pattern is:
if (m_signer)checks followed by method calls (frequent)std::atomic<T*>provides sequential consistency for these operations without the overhead of mutex locking. The usage would be:std::atomic<chainlock::ChainLockSigner*> m_signer{nullptr}; void ConnectSigner(gsl::not_null<chainlock::ChainLockSigner*> signer) { assert(m_signer.load() == nullptr); m_signer.store(signer); } void DisconnectSigner() { m_signer.store(nullptr); }And existing
if (m_signer)checks would becomeif (m_signer.load())or justif (m_signer)since atomic pointers have implicit conversion.This is much more efficient than mutex synchronization for this simple pointer swap pattern, especially given that reads are likely far more frequent than writes.
🧠 Learnings used