From: Michal Hocko <mhocko@kernel.org>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: rientjes@google.com, hannes@cmpxchg.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/oom: Suppress unnecessary "sharing same memory"message.
Date: Wed, 2 Sep 2015 16:24:47 +0200 [thread overview]
Message-ID: <20150902142447.GC8985@dhcp22.suse.cz> (raw)
In-Reply-To: <201509022027.AEH95817.VFFOHtMQOLFOJS@I-love.SAKURA.ne.jp>
On Wed 02-09-15 20:27:20, Tetsuo Handa wrote:
[...]
> >From 7268b614a159cd7cb307c7dfab6241b72d9cef93 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Wed, 2 Sep 2015 20:03:16 +0900
> Subject: [PATCH v2] mm/oom: Suppress unnecessary "sharing same memory" message.
>
> oom_kill_process() sends SIGKILL to other thread groups sharing
> victim's mm. But printing
>
> "Kill process %d (%s) sharing same memory\n"
>
> lines makes no sense if they already have pending SIGKILL.
> This patch reduces the "Kill process" lines by printing
> that line with info level only if SIGKILL is not pending.
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
I do not expect this would have a big effect in practice but it is true
that it saves some pointless output without clobbering the code much so
it makes sense to me.
Acked-by: Michal Hocko <mhocko@suse.com>
Wrt. pr_err -> pr_info I think this makes some sense as well because it
is true that users might intentionally push away the useful information
about the killed task this way. Not that it is a big problem but
still...
But who knows maybe somebody depends on this information even on the
pr_err loglevel. I know that David is relying on parsing oom reports
quite heavily so he might have more to tell about it.
> ---
> mm/oom_kill.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 1ecc0bc..610da01 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -576,9 +576,11 @@ void oom_kill_process(struct oom_control *oc, struct task_struct *p,
> !(p->flags & PF_KTHREAD)) {
> if (p->signal->oom_score_adj == OOM_SCORE_ADJ_MIN)
> continue;
> + if (fatal_signal_pending(p))
> + continue;
>
> task_lock(p); /* Protect ->comm from prctl() */
> - pr_err("Kill process %d (%s) sharing same memory\n",
> + pr_info("Kill process %d (%s) sharing same memory\n",
> task_pid_nr(p), p->comm);
> task_unlock(p);
> do_send_sig_info(SIGKILL, SEND_SIG_FORCED, p, true);
> --
> 1.8.3.1
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-09-02 14:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-29 11:14 [PATCH] mm/oom: Suppress unnecessary "sharing same memory" message Tetsuo Handa
2015-09-01 13:34 ` Michal Hocko
2015-09-02 11:27 ` [PATCH] mm/oom: Suppress unnecessary "sharing same memory"message Tetsuo Handa
2015-09-02 14:24 ` Michal Hocko [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-25 14:33 [PATCH] mm/oom: Suppress unnecessary "sharing same memory" message Tetsuo Handa
2015-05-26 17:02 ` Michal Hocko
2015-05-26 21:39 ` Tetsuo Handa
2015-05-27 16:45 ` Michal Hocko
2015-05-27 21:59 ` Tetsuo Handa
2015-05-28 18:05 ` Michal Hocko
2015-05-29 12:40 ` [PATCH] mm/oom: Suppress unnecessary "sharing same memory"message Tetsuo Handa
2015-05-29 14:49 ` Michal Hocko
2015-05-29 17:20 ` [PATCH] mm/oom: Suppress unnecessary "sharing same memory" message Tetsuo Handa
2015-05-31 11:10 ` Tetsuo Handa
2015-06-01 9:58 ` Michal Hocko
2015-06-01 10:16 ` Michal Hocko
2015-06-01 12:02 ` Tetsuo Handa
2015-06-01 12:15 ` Michal Hocko
2015-06-01 13:04 ` Tetsuo Handa
2015-06-01 13:12 ` Michal Hocko
2015-06-01 15:27 ` Tetsuo Handa
2015-06-01 15:42 ` Michal Hocko
2015-06-01 9:03 ` Michal Hocko
2015-06-01 10:51 ` Tetsuo Handa
2015-06-01 11:43 ` Michal Hocko
2015-06-01 12:10 ` Tetsuo Handa
2015-06-01 12:17 ` Michal Hocko
2015-06-01 12:34 ` Tetsuo Handa
2015-06-01 13:05 ` Michal Hocko
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=20150902142447.GC8985@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=hannes@cmpxchg.org \
--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;
as well as URLs for NNTP newsgroup(s).