-
Notifications
You must be signed in to change notification settings - Fork 37.7k
blockman: Properly guard blockfile members #24456
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
Conversation
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
422f1f3
to
1b95be4
Compare
1b95be4
to
f097cc3
Compare
🐙 This pull request conflicts with the target branch and needs rebase. Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft". |
Add GUARDED_BY(cs_LastBlockFile) annotations to: - m_blockfile_info - m_last_blockfile - m_check_for_pruning Add locking annotations as appropriate. [META] Some of these LOCK annotations will be turned into a AssertLockHeld+EXCLUSIVE_LOCKS_REQUIRED combo in the next commit
It is only used in CChainState::PreciousBlock with ::cs_main locked.
Not going to nurse this PR anymore, feel free to take for yourself! |
Logically a rebase of: #15191
Based on and split off from: #22564
Last commit arose out of review: #22564 (comment)