lkml.org 
[lkml]   [2015]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] bugfix oom kill init lead panic
On Mon, 30 Nov 2015 18:54:29 +0800 <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.
>
> ...
>
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -513,7 +513,7 @@ void oom_kill_process(struct task_struct *p, gfp_t gfp_mask, int order,
> rcu_read_lock();
> for_each_process(p)
> if (p->mm == mm && !same_thread_group(p, victim) &&
> - !(p->flags & PF_KTHREAD)) {
> + !(p->flags & PF_KTHREAD) && !is_global_init(p)) {
> if (p->signal->oom_score_adj == OOM_SCORE_ADJ_MIN)
> continue;

What kernel version are you using?

I don't think this can happen in current code...


\
 
 \ /
  Last update: 2015-11-30 04:21    [W:1.955 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site