From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@suse.cz
Cc: linux-mm@kvack.org
Subject: Re: [PATCH] mm/oom: Suppress unnecessary "sharing same memory" message.
Date: Mon, 1 Jun 2015 22:04:28 +0900 [thread overview]
Message-ID: <201506012204.GIF87536.LFMtOOOVJFFSQH@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20150601121508.GF7147@dhcp22.suse.cz>
Michal Hocko wrote:
> > Likewise, move do_send_sig_info(SIGKILL, victim) to before
> > mark_oom_victim(victim) in case for_each_process() took very long time,
> > for the OOM victim can abuse ALLOC_NO_WATERMARKS by TIF_MEMDIE via e.g.
> > memset() in user space until SIGKILL is delivered.
>
> This is unrelated and I believe even not necessary.
Why unnecessary? If serial console is configured and printing a series of
"Kill process %d (%s) sharing same memory" took a few seconds, the OOM
victim can consume all memory via malloc() + memset(), can't it?
What to do if the OOM victim cannot die immediately after consuming
all memory? I think that sending SIGKILL before setting TIF_MEMDIE
helps reducing consumption of memory reserves.
--
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-06-01 13:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2015-08-29 11:14 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
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=201506012204.GIF87536.LFMtOOOVJFFSQH@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
/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).