Hi Michal
I just rebase the patch from the latest version.


Michal Hocko <mhocko@kernel.org> 于2018年11月22日周四 下午9:39写道：

> On Wed 21-11-18 19:29:59, ufo19890607@gmail.com wrote:
> > From: yuzhoujian <yuzhoujian@didichuxing.com>
> >
> > 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 helpful for containerized environments to locate which
> > container has lost a process. 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.
> >
> > Below is the single line output in the oom report after this patch.
> > - global oom context information:
> >
> oom-kill:constraint=<constraint>,nodemask=<nodemask>,cpuset=<cpuset>,mems_allowed=<mems_allowed>,global_oom,task_memcg=<memcg>,task=<comm>,pid=<pid>,uid=<uid>
> > - memcg oom context information:
> >
> oom-kill:constraint=<constraint>,nodemask=<nodemask>,cpuset=<cpuset>,mems_allowed=<mems_allowed>,oom_memcg=<memcg>,task_memcg=<memcg>,task=<comm>,pid=<pid>,uid=<uid>
> >
> > Signed-off-by: yuzhoujian <yuzhoujian@didichuxing.com>
>
> I thought I have acked this one already.
> Acked-by: Michal Hocko <mhocko@suse.com>
> --
> Michal Hocko
> SUSE Labs
>