Skip to content
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

agent: Fix an issue reporting OOM events by mistake #8773

Merged
merged 1 commit into from
Jan 5, 2024

Commits on Jan 5, 2024

  1. agent: Fix an issue reporting OOM events by mistake

    The agent registers an event fd in `memory.oom_control`. An OOM event is
    forwarded to containerd when the event is emitted, regardless of the
    content in that file.
    
    I observed content indicating that events should not be forwarded, as shown
    below. When `oom_kill` is set to 0, it means no OOM has occurred. Therefore,
    it is important to check the content to avoid mistakenly forwarding OOM
    events.
    
    ```
    oom_kill_disable 0
    under_oom 0
    oom_kill 0
    ```
    
    Fixes: kata-containers#8715
    
    Signed-off-by: Xuewei Niu <niuxuewei.nxw@antgroup.com>
    justxuewei committed Jan 5, 2024
    Configuration menu
    Copy the full SHA
    0e9d73f View commit details
    Browse the repository at this point in the history