From: Michal Hocko <mhocko@kernel.org>
To: chenjie6@huawei.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David.Woodhouse@intel.com, zhihui.gao@huawei.com,
lizefan@huawei.com, akpm@linux-foundation.org,
stable@vger.kernel.org
Subject: Re: [PATCH] oom kill init lead panic
Date: Wed, 2 Dec 2015 11:35:49 +0100 [thread overview]
Message-ID: <20151202103549.GB25290@dhcp22.suse.cz> (raw)
In-Reply-To: <1449037856-23990-1-git-send-email-chenjie6@huawei.com>
On Wed 02-12-15 14:30:56, chenjie6@huawei.com wrote:
> From: chenjie <chenjie6@huawei.com>
>
> when oom happened we can see:
> 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
>
> That's because:
> the busybox init will vfork a process,oom_kill_process found
> the init not the children,their mm is the same when vfork.
It is quite unlikely that killing the task would help to free much
memory so if this is really the only oom victim it is to be expected to
panic sooner or later but this is in line with oom_unkillable_task()
so it makes sense.
> Cc: <stable@vger.kernel.org>
> Signed-off-by: Chen Jie <chenjie6@huawei.com>
Acked-by: Michal Hocko <mhocko@suse.com>
>
> ---
> mm/oom_kill.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index d13a339..a0ddebd 100644
> --- 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;
>
> --
> 1.8.0
>
> --
> 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>
--
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-02 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 6:30 chenjie6
2015-12-02 10:35 ` Michal Hocko [this message]
2015-12-02 15:47 ` Greg KH
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=20151202103549.GB25290@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=stable@vger.kernel.org \
--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