cgroup: Support 0-value for memory protection directives
These make sense to be explicitly set at 0 (which has a different effect than the default, since it can affect processing of `DefaultMemoryXXX`). Without this, it's not easily possible to relinquish memory protection for a subtree, which is not great.
Loading
Please register or sign in to comment