-
Notifications
You must be signed in to change notification settings - Fork 6
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
waitgroup sync fix #37
Merged
Merged
Conversation
This file contains 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
tklauser
reviewed
May 20, 2022
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.
One comment about golangci-lint version, all other commits LGTM. Thanks.
e7cacc4
to
fa320d0
Compare
fa320d0
to
ef0b159
Compare
Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
Bring workerpool in line with how license / copyright is handled in Cilium, see cilium/cilium#18813 for more context. Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
Drain() doesn't submit any task. Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
tklauser
approved these changes
May 20, 2022
rolinh
reviewed
May 20, 2022
rolinh
approved these changes
May 20, 2022
ef0b159
to
f5473ba
Compare
Before this patch, Submit() would increment the WaitGroup without holding the WorkerPool lock. This could potentially lead to a panic when Submit() and Close() were executed concurrently: 1. The Submit() goroutine g0 acquire the lock, successfully check that the WorkerPool is neither closed nor draining, and release the lock. 2. The Close() goroutine g1 acquire the lock, update the WorkerPool state to closed, wait on the WaitGroup, and close the tasks channel (wrongly) assuming that all tasks have been submitted. 3. g0 increment the WaitGroup, and attempt to write to the (now closed) tasks channel leading to a panic. The same reasoning can be applied with Submit() and Drain() leading to a data race on the results slice. Signed-off-by: Alexandre Perrin <alex@kaworu.ch>
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.
See commits, the most important one is the last one workerpool: WaitGroup synchronization fix.