From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: 禹舟键 <ufo19890607@gmail.com>,
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" <yuzhoujian@didichuxing.com>
Subject: Re: [PATCH v15 2/2] Add oom victim's memcg to the oom context information
Date: Wed, 19 Dec 2018 10:39:38 +0100 [thread overview]
Message-ID: <20181219093938.GA5758@dhcp22.suse.cz> (raw)
In-Reply-To: <201812190723.wBJ7NdkN032628@www262.sakura.ne.jp>
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 <penguin-kernel@I-love.SAKURA.ne.jp>
> 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 <penguin-kernel@I-love.SAKURA.ne.jp>
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
next prev parent reply other threads:[~2018-12-19 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 11:29 [PATCH v15 1/2] Reorganize the oom report in dump_header ufo19890607
2018-11-21 11:29 ` [PATCH v15 2/2] Add oom victim's memcg to the oom context information ufo19890607
2018-11-22 13:39 ` Michal Hocko
2018-11-23 6:11 ` 禹舟键
2018-12-19 7:23 ` Tetsuo Handa
2018-12-19 9:39 ` Michal Hocko [this message]
2018-11-22 13:38 ` [PATCH v15 1/2] Reorganize the oom report in dump_header Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2018-09-29 13:06 ufo19890607
2018-09-29 13:06 ` [PATCH v15 2/2] Add oom victim's memcg to the oom context information ufo19890607
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181219093938.GA5758@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.com \
--cc=ufo19890607@gmail.com \
--cc=yang.s@alibaba-inc.com \
--cc=yuzhoujian@didichuxing.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox