-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
chainlocks: Fix potential deadlock #3972
Conversation
Should fix this: ``` Previous lock order was: pnode->cs_sendProcessing net.cpp:2854 cs_main net_processing.cpp:3946 (TRY) mempool.cs net_processing.cpp:4183 (1) pto->cs_inventory net_processing.cpp:4183 pto->cs_filter net_processing.cpp:4233 (2) cs llmq/quorums_chainlocks.cpp:87 Current lock order is: cs_main llmq/quorums_chainlocks.cpp:138 (2) cs llmq/quorums_chainlocks.cpp:138 cs_vNodes net.cpp:3662 (1) cs_inventory ./net.h:1085 ```
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.
Couldn't we then also move InternalHasConflictingChainLock
up into the other LOCK(cs)
scope (without negative side effects?) like in 5b520c3?
I guess 5b520c3 makes sense. Just not in this PR :) |
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
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
Should fix this: ``` Previous lock order was: pnode->cs_sendProcessing net.cpp:2854 cs_main net_processing.cpp:3946 (TRY) mempool.cs net_processing.cpp:4183 (1) pto->cs_inventory net_processing.cpp:4183 pto->cs_filter net_processing.cpp:4233 (2) cs llmq/quorums_chainlocks.cpp:87 Current lock order is: cs_main llmq/quorums_chainlocks.cpp:138 (2) cs llmq/quorums_chainlocks.cpp:138 cs_vNodes net.cpp:3662 (1) cs_inventory ./net.h:1085 ```
Should fix this: