linux-kernel - Re: oom_killer crash linux system

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20101019152249.e268b1e9.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Tue, 19 Oct 2010 15:22:49 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	"Figo.zhang" <zhangtianfei@...dcoretech.com>
Cc:	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Wu Fengguang <fengguang.wu@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"rientjes@...gle.com" <rientjes@...gle.com>,
	figo1802 <figo1802@...il.com>
Subject: Re: oom_killer crash linux system

On Tue, 19 Oct 2010 10:07:38 +0800
"Figo.zhang" <zhangtianfei@...dcoretech.com> wrote:

> 
> > 
> > very lots of change ;)
> > can you please send us your crash log?
> 
> i add some prink in select_bad_process() and oom_badness() to see
> pid/totalpages/points/memoryuseage/and finally process to selet to kill.
> 
> i found it the oom-killer select: syslog-ng,mysqld,nautilus,VirtualBox
> to kill, so my question is:
> 
please show your patch..for getting logs.

It seems you added printke to here.
>                 if (points > *ppoints) {
>                         chosen = p;
>                         *ppoints = points;
>                 }

So, finally _a_ chosen process is ....

> ===========have choose pid=1304 to kill, points=1

> Oct 19 09:44:08 myhost kernel: [  618.441168] oom_badness: memoy use
> =4346, totalpages=506807, points=8
...
> Oct 19 09:44:08 myhost kernel: [  618.441170] oom_badness: pid = 2065,
> oom_score_adj=0, points=8
> Oct 19 09:44:08 myhost kernel: [  618.441171] select_bad_process,
> pid=2065, points=8
> Oct 19 09:44:08 myhost kernel: [  618.441172] select_bad_process,
> ===========have choose pid=2065 to kill, points=8
...
> Oct 19 09:44:08 myhost kernel: [  618.441189] oom_badness: memoy use
> =18211, totalpages=506807, points=35
> Oct 19 09:44:08 myhost kernel: [  618.441190] oom_badness: pid = 2078,
> oom_score_adj=0, points=35
> Oct 19 09:44:08 myhost kernel: [  618.441191] select_bad_process,
> pid=2078, points=35
> Oct 19 09:44:08 myhost kernel: [  618.441193] select_bad_process,
> ===========have choose pid=2078 to kill, points=35
...
> Oct 19 09:44:08 myhost kernel: [  618.441356] oom_badness: memoy use
> =278247, totalpages=506807, points=549
> Oct 19 09:44:08 myhost kernel: [  618.441358] oom_badness: pid = 2646,
> oom_score_adj=0, points=549
> Oct 19 09:44:08 myhost kernel: [  618.441359] select_bad_process,
> pid=2646, points=549
> Oct 19 09:44:08 myhost kernel: [  618.441360] select_bad_process,
> ===========have choose pid=2646 to kill, points=549

> Oct 19 09:44:08 myhost kernel: [  618.441470] httpd invoked oom-killer:
> gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0
> Oct 19 09:44:08 myhost kernel: [  618.441473] httpd cpuset=/
> mems_allowed=0

PID 2646, Virtual Box. Right ?

I think you have a log message as.
==
        pr_err("Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%lukB\n",
                task_pid_nr(p), p->comm, K(p->mm->total_vm),
                K(get_mm_counter(p->mm, MM_ANONPAGES)),
                K(get_mm_counter(p->mm, MM_FILEPAGES)));
==
... and killed one is Virtual box.(and syslog-ng etc.. aren't killed.)

Thanks,
-Kame


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/