Chris Down
4fb8cc53b3
Consider a workload slice with several sibling cgroups. Imagine that one of those cgroups is removed between the moment oomd enumerates the directory and the moment it reads memory.oom.group. This is actually relatively plausible under the high memory pressure conditions where oomd is most needed. In this case, the failed read prompts us to `return 0`, which exits the entire enumeration loop in recursively_get_cgroup_context(). As a result, all remaining sibling cgroups are silently dropped from the candidate list for that monitoring cycle. The effect is that oomd can fail to identify and kill the actual offending cgroup, allowing memory pressure to persist until a subsequent cycle where the race doesn't occur. Fix this by instead proceeding to evaluate further sibling cgroups.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list, join our IRC channel #systemd on libera.chat or Matrix channel
Stable branches with backported patches are available in the stable repo.
We have a security bug bounty program sponsored by the Sovereign Tech Fund hosted on YesWeHack
Repositories with distribution packages built from git main are available on OBS, and also repositories with packages built from the latest stable release