linux-kernel - Runaway process and oom-killer

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-next>] [day] [month] [year] [list]

Date:	Wed, 13 Jun 2007 10:49:29 +0200
From:	John Sigler <linux.kernel@...e.fr>
To:	linux-kernel@...r.kernel.org
Subject: Runaway process and oom-killer

Hello,

I have a problem with an app I wrote: after it has run for a long time 
(sometimes 10-15 hours, sometimes several days) the oom-killer kicks in 
and snipes most processes in the system.

(My process runs in SCHED_RR.)

There is a good probability that there is a memory leak in my app, but 
I'm trying to make sense of the oom-killer's logs to make sure.

If I run dmesg, it prints the oom-killer's logs.

Question 1: why isn't this output picked up by klogd and sent to the 
appropriate file (kern.log in my case)?

Question 2: how can I tell which process or kernel thread was hogging 
most of the RAM when the oom-killer kicked in?

Question 3: if myapp was hogging the RAM, then why did oom-killer snipe 
other processes (syslogd and boa) after it killed myapp?

Regards.

View attachment "dmesg.txt" of type "text/plain" (14485 bytes)