From: Michal Hocko <mhocko@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: rientjes@google.com, penguin-kernel@i-love.sakura.ne.jp,
akpm@linux-foundation.org, cai@lca.pw, linux-mm@kvack.org
Subject: Re: [PATCH v2] mm, oom: show process exiting information in __oom_kill_process()
Date: Tue, 21 Jul 2020 08:06:15 +0200 [thread overview]
Message-ID: <20200721060615.GF4061@dhcp22.suse.cz> (raw)
In-Reply-To: <20200721010127.17238-1-laoar.shao@gmail.com>
On Mon 20-07-20 21:01:27, Yafang Shao wrote:
> When the OOM killer finding a victim and trying to kill it, if the victim
> is already exiting, the task mm will be NULL and no process will be killed.
> But the dump_header() has been already executed, so it will be strange to
> dump so many information without killing a process. We'd better show some
> helpful information to indicate why this happens.
>
> Suggested-by: David Rientjes <rientjes@google.com>
> Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
> Cc: Michal Hocko <mhocko@kernel.org>
> Cc: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
> Cc: Qian Cai <cai@lca.pw>
Acked-by: Michal Hocko <mhocko@suse.com>
Thanks!
> ---
> v1 -> v2:
> - improve the output, per Tetsuo and Michal
> ---
> mm/oom_kill.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 6e94962893ee..c176c988c109 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -863,6 +863,8 @@ static void __oom_kill_process(struct task_struct *victim, const char *message)
>
> p = find_lock_task_mm(victim);
> if (!p) {
> + pr_info("%s: OOM victim %d (%s) is already exiting. Skip killing the task\n",
> + message, task_pid_nr(victim), victim->comm);
> put_task_struct(victim);
> return;
> } else if (victim != p) {
> --
> 2.18.1
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2020-07-21 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-21 1:01 Yafang Shao
2020-07-21 6:06 ` Michal Hocko [this message]
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=20200721060615.GF4061@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cai@lca.pw \
--cc=laoar.shao@gmail.com \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=rientjes@google.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