Fix OOM watcher for cgroupv2 oom_kill events
#1054
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
It may be possible that the container process already got signaled but is still running, whereas we will not get a `modify` (but `other`) event on the file watcher. Beside that, it will also not update the `oom` entry of `memory.events`, but the `oom_kill`, which provides another indicator for a possible out of memory kill. Ref: https://www.kernel.org/doc/Documentation/cgroup-v2.txt Signed-off-by: Sascha Grunert <sgrunert@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This was referenced Jan 31, 2023
|
/lgtm |
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.
What type of PR is this?
/kind bug
What this PR does / why we need it:
It may be possible that the container process already got signaled but is still running, whereas we will not get a
modify(butother) event on the file watcher. Beside that, it will also not update theoomentry ofmemory.events, but theoom_kill, which provides another indicator for a possible out of memory kill.Ref: https://www.kernel.org/doc/Documentation/cgroup-v2.txt
Which issue(s) this PR fixes:
Adresses cri-o/cri-o#6580 for the conmon-rs usage
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?