Fix suboptimal lock release in (*handler).getChainInfo
.
#733
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.
Possible source of bugs in the future but not currently a problem, as
h.chainInfo
is never set tonil
but fromnil
.getChainInfo
could sometimes unnecessarily returnnil
ifh.chainInfo
were set tonil
after releasing theh.chainInfoLk
read lock.Also remove direct, unsynchronized access to
h.chainInfo
inh.getRand()
. Similarly not a bug in the current usage, but could be a source of crashes ifh.chainInfo
is set tonil
, orh.getRand()
isn't called after a previous call toh.getChainInfo()