-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
libcontainer/cgroups: do not enable kmem on broken kernels #1920
Closed
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
Wondering if it should be a compile time option, so that packagers for a specific distro can enable/disable it |
Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
Commit fe898e7 (PR opencontainers#1350) enables kernel memory accounting for all cgroups created by libcontainer even if kmem limit is not configured. Kernel memory accounting is known to be broken in RHEL7 kernels, including the latest RHEL 7.5 kernel. It does not support reclaim and can lead to kernel oopses while removing cgroup (merging it with its parent). Unconditionally enabling kmem acct on RHEL7 leads to bugs: * opencontainers#1725 * kubernetes/kubernetes#61937 * moby/moby#29638 I am not aware of any good way to figure out whether the kernel memory accounting in the given kernel is working or broken. For the lack of a better way, let's check if the running kernel is RHEL7, and disable initial setting of kmem. Signed-off-by: Kir Kolyshkin <kolyshkin@gmail.com>
cc @mrunalp |
Apparently the kernel bug(s) we work around here are not fixed in latest-n-greatest RHEL7.6 kernels (see latest comments in https://bugzilla.redhat.com/show_bug.cgi?id=1507149). |
I prefer #1921 and have LGTM'ed it. Thanks! |
NACK. I prefer #1921 as well. |
Closed in favor of #1921 |
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.
Commit fe898e7 (PR #1350) enables kernel memory accounting for all cgroups created by libcontainer even if kmem limit is not configured.
Kernel memory accounting is known to be broken in RHEL7 kernels,
including the latest RHEL 7.5 kernel. It does not support reclaim
and can lead to kernel oopses while removing cgroup (merging it
with its parent). Unconditionally enabling kmem acct on RHEL7
leads to bugs:
I am not aware of any good way to figure out whether the kernel
memory accounting in the given kernel is working or broken.
For the lack of a better way, let's check if the running kernel
is RHEL7, and disable initial setting of kmem.
Alternative to #1898