From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <owner-linux-mm@kvack.org>
Received: from mail-wr0-f198.google.com (mail-wr0-f198.google.com [209.85.128.198])
	by kanga.kvack.org (Postfix) with ESMTP id 9A4EC6B0005
	for <linux-mm@kvack.org>; Thu, 31 May 2018 02:49:55 -0400 (EDT)
Received: by mail-wr0-f198.google.com with SMTP id 33-v6so15982372wrb.12
        for <linux-mm@kvack.org>; Wed, 30 May 2018 23:49:55 -0700 (PDT)
Received: from mx2.suse.de (mx2.suse.de. [195.135.220.15])
        by mx.google.com with ESMTPS id r5-v6si1830072edm.42.2018.05.30.23.49.53
        for <linux-mm@kvack.org>
        (version=TLS1 cipher=AES128-SHA bits=128/128);
        Wed, 30 May 2018 23:49:54 -0700 (PDT)
Date: Thu, 31 May 2018 08:49:51 +0200
From: Michal Hocko <mhocko@kernel.org>
Subject: Re: [PATCH v4] Print the memcg's name when system-wide OOM happened
Message-ID: <20180531064951.GG15278@dhcp22.suse.cz>
References: <1526870386-2439-1-git-send-email-ufo19890607@gmail.com>
 <20180530134256.bbf7a8639571a3f8910b6a05@linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180530134256.bbf7a8639571a3f8910b6a05@linux-foundation.org>
Sender: owner-linux-mm@kvack.org
List-ID: <linux-mm.kvack.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: ufo19890607 <ufo19890607@gmail.com>, rientjes@google.com, kirill.shutemov@linux.intel.com, aarcange@redhat.com, penguin-kernel@I-love.SAKURA.ne.jp, guro@fb.com, yang.s@alibaba-inc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, yuzhoujian <yuzhoujian@didichuxing.com>

On Wed 30-05-18 13:42:56, Andrew Morton wrote:
> On Mon, 21 May 2018 03:39:46 +0100 ufo19890607 <ufo19890607@gmail.com> wrote:
> 
> > From: yuzhoujian <yuzhoujian@didichuxing.com>
> > 
> > The dump_header does not print the memcg's name when the system
> > oom happened. So users cannot locate the certain container which
> > contains the task that has been killed by the oom killer.
> > 
> > System oom report will print the memcg's name after this patch,
> > so users can get the memcg's path from the oom report and check
> > the certain container more quickly.
> 
> lkp-robot is reporting an oops.
> 
> > --- a/mm/oom_kill.c
> > +++ b/mm/oom_kill.c
> > @@ -433,6 +433,7 @@ static void dump_header(struct oom_control *oc, struct task_struct *p)
> >  	if (is_memcg_oom(oc))
> >  		mem_cgroup_print_oom_info(oc->memcg, p);
> >  	else {
> > +		mem_cgroup_print_oom_memcg_name(oc->memcg, p);
> >  		show_mem(SHOW_MEM_FILTER_NODES, oc->nodemask);
> >  		if (is_dump_unreclaim_slabs())
> >  			dump_unreclaimable_slab();
> 
> static inline bool is_memcg_oom(struct oom_control *oc)
> {
> 	return oc->memcg != NULL;
> }
> 
> So in the mem_cgroup_print_oom_memcg_name() call which this patch adds,
> oc->memcg is known to be NULL.  How can this possibly work?  

This version is broken. The current version [1] seems to be doing the
right thing in that regards AFAICS. It has some other issues though.
Can we drop the current code from the mmotm tree and start over?

[1] http://lkml.kernel.org/r/1527413551-5982-1-git-send-email-ufo19890607@gmail.com
-- 
Michal Hocko
SUSE Labs