-
-
Notifications
You must be signed in to change notification settings - Fork 600
fix(healthcheck): guard periodic checks against divide-by-zero when config is cleared #3400
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
Open
mvanhorn
wants to merge
1
commit into
passteque:master
Choose a base branch
from
mvanhorn:fix/3398-healthcheck-divide-by-zero
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+27
−1
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
Because above we run
c.stop()to cancel the long running goroutine and wait for<-c.done, the long running goroutine should be finished and so there should be no need to hold a mutex here I think. I'll dig into this, to avoid these AI-bandaid-fixes (that do the job, but it does bloat code whereas it does not fix the real source of the problem)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.
You're right that after c.stop() and <-c.done the periodic goroutine can't touch these fields, so the lock in Stop isn't about that goroutine. What it guards is SetConfig: Stop runs on the collectHealthErrors goroutine (started at tunnelup.go:107, calls Stop at 148/156) while SetConfig runs on the VPN loop goroutine in onTunnelUp (tunnelup.go:88). If the loop state machine already guarantees those never overlap across a restart cycle, then the Stop hunk is redundant and I'm happy to drop it.
The part I'd keep either way is fullPeriodicCheck: on master it indexes c.tlsDialAddrs unlocked, while smallPeriodicCheck copies under the same mutex for the same fields, so this just makes the two checks consistent. The empty-slice guards also protect the try%len modulo from a divide-by-zero panic when the config is empty.
Happy to trim the PR to whichever subset you want after you've dug in.