From: Michal Hocko <mhocko@kernel.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
chenjie6@huawei.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, David.Woodhouse@intel.com,
zhihui.gao@huawei.com, lizefan@huawei.com
Subject: Re: [patch] mm, oom: avoid attempting to kill init sharing same memory
Date: Thu, 3 Dec 2015 09:12:01 +0100 [thread overview]
Message-ID: <20151203081200.GA9264@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.10.1512021509460.14638@chino.kir.corp.google.com>
On Wed 02-12-15 15:10:28, David Rientjes wrote:
> From: Chen Jie <chenjie6@huawei.com>
>
> It's possible that an oom killed victim shares an ->mm with the init
> process and thus oom_kill_process() would end up trying to kill init as
> well.
>
> This has been shown in practice:
>
> Out of memory: Kill process 9134 (init) score 3 or sacrifice child
> Killed process 9134 (init) total-vm:1868kB, anon-rss:84kB, file-rss:572kB
> Kill process 1 (init) sharing same memory
> ...
> Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
>
> And this will result in a kernel panic.
>
> If a process is forked by init and selected for oom kill while still
> sharing init_mm, then it's likely this system is in a recoverable state.
> However, it's better not to try to kill init and allow the machine to
> panic due to unkillable processes.
>
> [rientjes@google.com: rewrote changelog]
> Acked-by: Michal Hocko <mhocko@suse.com>
> Signed-off-by: Chen Jie <chenjie6@huawei.com>
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
> I removed stable from this patch since the alternative would most likely
> be to panic the system for no killable processes anyway. There's a very
> small likelihood this patch would allow for a recoverable system.
Agreed.
> mm/oom_kill.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -608,6 +608,8 @@ void oom_kill_process(struct oom_control *oc, struct task_struct *p,
> continue;
> if (unlikely(p->flags & PF_KTHREAD))
> continue;
> + if (!is_global_init(p))
> + continue;
> if (p->signal->oom_score_adj == OOM_SCORE_ADJ_MIN)
> continue;
>
--
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-12-03 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 23:10 [patch] mm, oom: avoid attempting to kill init sharing same memory David Rientjes
2015-12-03 8:12 ` Michal Hocko [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-12-03 8:19 Hillf Danton
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=20151203081200.GA9264@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=David.Woodhouse@intel.com \
--cc=akpm@linux-foundation.org \
--cc=chenjie6@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=rientjes@google.com \
--cc=zhihui.gao@huawei.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).