Add bounds on max oom_score_adj value for AdjustOOMScore#4845
Add bounds on max oom_score_adj value for AdjustOOMScore#4845estesp merged 1 commit intocontainerd:masterfrom skaegi:oom_score-max
Conversation
|
Hi @skaegi. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
/ok-to-test |
|
Build succeeded.
|
|
Build succeeded.
|
|
Build succeeded.
|
|
Looks like you don't have a valid DCO on all commits. It is probably better if you just squash these commits together and make sure it's signed. |
oom_score_adj must be in the range -1000 to 1000. In AdjustOOMScore if containerd's score is already at the maximum value we should set that value for the shim instead of trying to set 1001 which is invalid. Signed-off-by: Simon Kaegi <[email protected]>
|
Build succeeded.
|
|
I wasn't sure how to write a unit test that exercised this particular case but did run a manual test to confirm our CI case works by patching docker:20-dind and validating in my environment where the oom_score_adj is 1000. Is there anything more to do here? The one failing test above seems unrelated and perhaps an intermittent issue?? |
oom_score_adj must be in the range -1000 to 1000. In AdjustOOMScore if containerd's score is already at the maximum value we should set that value for the shim instead of trying to set 1001 which is invalid.
Fixes #4837
Signed-off-by: Simon Kaegi [email protected]