-
Notifications
You must be signed in to change notification settings - Fork 725
[Refactor] Strip out cs_main lock for misbehaving from Masternodeman:ProcessMessage #1922
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
[Refactor] Strip out cs_main lock for misbehaving from Masternodeman:ProcessMessage #1922
Conversation
ece5447 to
2e29c4c
Compare
|
now that #1845 got merged, PR rebased. |
random-zebra
left a comment
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.
Looking good.
But I think it could be simplified by having the Process* methods return a simple integer representing the ban score, rather than the new struct ProcessResult (whose boolean res seems redundant: if the ban score is 0 we don't call Misbehaving regardless of the value of res).
Special attention needed for CTxIn::IsNull.
2e29c4c to
c8717d9
Compare
|
Updated per feedback. |
…aving call from its flow.
…ing call from its flow
… ProcessMessage below ProcessGetMNList.
…cast hash only once.
c8717d9 to
50e156f
Compare
|
rebased on master. |
random-zebra
left a comment
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.
utACK 50e156f
Fuzzbawls
left a comment
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.
utACK 50e156f
Built on top of #1845.
Refactored
Masternodeman:ProcessMessagedecoupling in different methods and stripped out everycs_mainlock for aMisbehavingfunction call.