-
Notifications
You must be signed in to change notification settings - Fork 1.1k
oci: Fix a couple of deadlocks in container stop code #5433
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
Signed-off-by: Peter Hunt <[email protected]>
Signed-off-by: Peter Hunt <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #5433 +/- ##
=======================================
Coverage 43.46% 43.47%
=======================================
Files 118 118
Lines 11848 11851 +3
=======================================
+ Hits 5150 5152 +2
Misses 6206 6206
- Partials 492 493 +1 |
|
for reference, we have a goroutine stack that has a ridiculous number of go routines stuck on this line While this more seems like the go routine didn't receive correctly on the close of chControl, adding the buffer would also let the function make forward progress. i.e. I am suspecting something funky about the go runtime, but maybe we can work around it? |
|
/retest |
saschagrunert
left a comment
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.
LGTM
|
/test e2e-agnostic |
|
/retest-required |
|
so I didn't actually know why this could work but I guessed it would. Figured it out chatting with @rphillips today: if chControl is closed while UpdateContainerStatus is running, we will wait forever on done, when we should check chControl. buffering the channel will allow us to make forward progress (without really complicating the code that much) |
Signed-off-by: Peter Hunt <[email protected]>
|
/retest |
1 similar comment
|
/retest |
|
@cri-o/cri-o-maintainers PTAL |
|
/retest |
saschagrunert
left a comment
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.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@haircommander: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
/cherry-pick release-1.22 |
|
@haircommander: once the present PR merges, I will cherry-pick it on top of release-1.22 in a new PR and assign it to you. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
|
/retest-required Please review the full test history for this PR and help us cut down flakes. |
|
@haircommander: #5433 failed to apply on top of branch "release-1.22": DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?