On Tue 03-09-19 20:20:20, Thomas Lindroth wrote: [...] > If kmem accounting is both broken, unfixable and cause kernel crashes when > used why not remove it? Or perhaps disable it per default like > cgroup.memory=nokmem or at least print a warning to dmesg if the user tries > to user it in a way that cause crashes? Well, cgroup v1 interfaces and implementation is mostly frozen and users are advised to use v2 interface that doesn't suffer from this problem because there is no separate kmem limit and both user and kernel charges are tight to the same counter. We can be more explicit about shortcomings in the documentation but in general v1 is deprecated. -- Michal Hocko SUSE Labs
