On Fri, Dec 01, 2017 at 09:41:13AM +0100, Michal Hocko wrote: > On Thu 30-11-17 15:28:22, Roman Gushchin wrote: > > Add a "groupoom" cgroup v2 mount option to enable the cgroup-aware > > OOM killer. If not set, the OOM selection is performed in > > a "traditional" per-process way. > > > > The behavior can be changed dynamically by remounting the cgroupfs. > > Is it ok to create oom_group if the option is not enabled? This looks > confusing. I forgot all the details about how cgroup core creates file > so I do not have a good idea how to fix this. I don't think we do show/hide interface files dynamically. Even for things like socket memory which can be disabled by the boot option, we don't hide the corresponding stats entry. So, maybe we just need to return -EAGAIN (or may be -ENOTSUP) on any read/write attempt if option is not enabled? Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
