On Sun 01-07-18 00:38:59, ufo19890607@xxxxxxxxx wrote: > From: yuzhoujian <yuzhoujian@xxxxxxxxxxxxxxx> > > Add a new func mem_cgroup_print_oom_context to print missing information > for the system-wide oom report which includes the oom memcg that has > reached its limit, task memcg that contains the killed task. A proper changelog should contain the motivation. It is trivial to see what the patch does from the diff. The motivation is less clear. What about the followig " The current oom report doesn't display victim's memcg context during the global OOM situation. While this information is not strictly needed it can be really usefule for containerized environments to see which container has lost a process (+ add more arguments I am just guessing from your not really specific statements). Now that we have a single line for the oom context we can trivially add both the oom memcg (this can be either global_oom or a specific memcg which hits its hard limits) and task_memcg which is the victim's memcg. " -- Michal Hocko SUSE Labs
