eth: continue after whitelist check#24210
Merged
karalabe merged 1 commit intoethereum:masterfrom Jan 7, 2022
Merged
Conversation
Contributor
Author
Without the PR, on shutdown, a lot of peers are stuck on This is due (I think) to the peer threads being stuck waiting for the res to return here: |
Member
|
Good catch. @holiman Are the hangs before or after this PR? |
Contributor
Author
|
The hangs are without this PR (edited to clarify) |
sidhujag
pushed a commit
to syscoin/go-ethereum
that referenced
this pull request
Jan 11, 2022
eth: continue after whitelist check
Member
|
For inclusivity should we rename it to allowlist? |
Contributor
I definitely agree a more inclusive (and descriptive!) name would be better, I'll start a PR that deprecates the current name and chooses a new one as soon as I can, will link it here when ready. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The whitelist mechanism got broken in #23576, afaict, making it so that if the whitelist check succeeds, the code stalls. The peer is left somehow neither accepted nor rejected, in a state where it's marked as shutting down but not actually kicked out.
This is the cause behind #24202 .
Also, aside from not being able to sync, it also (on my test) causes failure to shut down.
With this fix, I was able to start syncing with peers after the check completes.