On Mon, 30 Nov 2015 18:54:29 +0800 <[email protected]> wrote: > From: chenjie <[email protected]> > > 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... -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
