Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp5031421imu; Wed, 19 Dec 2018 04:33:54 -0800 (PST) X-Google-Smtp-Source: AFSGD/XHvj4wgoOEiZukDRauZcnUkG3rVERjv6pQ0GKLWBgS10EkyJyxQD0/DMLr/TYR5UtcpEti X-Received: by 2002:a62:1d4c:: with SMTP id d73mr20537946pfd.90.1545222834274; Wed, 19 Dec 2018 04:33:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1545222834; cv=none; d=google.com; s=arc-20160816; b=ZNwm9WpGeupfiVdLlzq1TBgc4X7VGAL4Fk5MYjvhNdtSM0gRe2cCAVcyRzsEaJcSe8 b/Nz/1LlIre2tjMszNpF2TR7b5UYbGvj82wfgqKf5GhfOP+Krg9Avs5NP6eV+sWWCIB1 g29bJghEbpJdcATjK6V5sflGQ1MUv4/1FEfRvEmc9nJc394FaQpHcEjHxjMaxOPcH9Ds AsXKS6rXGxUWfcLnqtTRlzBqDYF32Cy7rOv7lDjyImrIz6wbZxSfgVOyYQe73hrSCvaX 0P5PF5nV/HA+IAx1qy2IQVqvQV/NhVc6CloN4RneqQbr2gRdqiqOpoGMZMdnQArVBWVp Tukw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=0Q3M0LUmjRbyJJCESpA5JJUnxGZetT6vOCBZcklgw04=; b=KJ+Y9DWomIZ/6k4DpsJUSLzyUeZKgM7rOVpGHgahVtunCPkRTRne4B3QzhS/kn1TNZ 8mA1F6F9ekLRzDq4P6LzKioyqBknUEbgXOUGbiujbZ9bK20FapQUluK+sbRfRi/+ULMP LRjbOq+kHFcbOfikEDS8UX4Hvvi69XxCuOMuSu0mOw7EXbl9uahng4lRdD+uxkrIkvl0 l6o2kpJhpHc+Hd8aYcgJzil2yEBqQw9PRY7KEw2GqlE46f2BSIQFFkQTi6yIINU12pkJ EJhULN9XqFnbQUuquynKsnkLKoH/QHc/jvMjAPFMKL5eIoOexJhg05cub8EIxbje0si9 Tldg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 1si15273426pld.239.2018.12.19.04.33.38; Wed, 19 Dec 2018 04:33:54 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728640AbeLSJjm (ORCPT + 99 others); Wed, 19 Dec 2018 04:39:42 -0500 Received: from mx2.suse.de ([195.135.220.15]:59550 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726537AbeLSJjl (ORCPT ); Wed, 19 Dec 2018 04:39:41 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id DE963ACEA; Wed, 19 Dec 2018 09:39:39 +0000 (UTC) Date: Wed, 19 Dec 2018 10:39:38 +0100 From: Michal Hocko To: Tetsuo Handa Cc: =?utf-8?B?56a56Iif6ZSu?= , akpm@linux-foundation.org, rientjes@google.com, kirill.shutemov@linux.intel.com, aarcange@redhat.com, guro@fb.com, yang.s@alibaba-inc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wind Yu Subject: Re: [PATCH v15 2/2] Add oom victim's memcg to the oom context information Message-ID: <20181219093938.GA5758@dhcp22.suse.cz> References: <20181122133954.GI18011@dhcp22.suse.cz> <201812190723.wBJ7NdkN032628@www262.sakura.ne.jp> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201812190723.wBJ7NdkN032628@www262.sakura.ne.jp> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 19-12-18 16:23:39, Tetsuo Handa wrote: > Andrew, will you fold below diff into "mm, oom: add oom victim's memcg to the oom context information" ? > > >From add1e8daddbfc5186417dbc58e9e11e7614868f8 Mon Sep 17 00:00:00 2001 > From: Tetsuo Handa > Date: Wed, 19 Dec 2018 16:09:31 +0900 > Subject: [PATCH] mm, oom: Use pr_cont() in mem_cgroup_print_oom_context(). > > One line summary of the OOM killer context is not one line due to > not using KERN_CONT. > > [ 23.346650] oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0 > [ 23.346691] ,global_oom,task_memcg=/,task=firewalld,pid=5096,uid=0 > > Signed-off-by: Tetsuo Handa Sorry, I have missed that during review. Thanks for catching this up! > --- > mm/memcontrol.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > index b860dd4f7..4afd597 100644 > --- a/mm/memcontrol.c > +++ b/mm/memcontrol.c > @@ -1306,10 +1306,10 @@ void mem_cgroup_print_oom_context(struct mem_cgroup *memcg, struct task_struct * > rcu_read_lock(); > > if (memcg) { > - pr_info(",oom_memcg="); > + pr_cont(",oom_memcg="); > pr_cont_cgroup_path(memcg->css.cgroup); > } else > - pr_info(",global_oom"); > + pr_cont(",global_oom"); > if (p) { > pr_cont(",task_memcg="); > pr_cont_cgroup_path(task_cgroup(p, memory_cgrp_id)); > -- > 1.8.3.1 -- Michal Hocko SUSE Labs