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  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:	Fri, 07 Dec 2007 10:25:23 +0100
From:	Martin MOKREJŠ <>
To:	LKML <>
Subject: OOM killer kills wrong jobs

  first of all, sorry for not being up to date with how the OOM killer
works. I think there used to be a kernel config option to disable
OOM killer and instead kill the process which actually asks for the
memory and supposedly caused the memory lack. That is what I would
like to have on my system. I a have a 1GB RAM laptop and use t-coffee
software from
to do some science. ;) 

# grep Killed /tmp/dmesg.killed.txt 
Killed process 5733 (seamonkey-bin)
Killed process 10011 (t_coffee)
Killed process 5647 (FvwmPager)
Killed process 5659 (xterm)

Killing just t_coffee would have been enough.

$ perl -e 'print ">one\n"; print "ATGCCGTAAATGCATG"x100000; print "\n>two"; print "GGGGCCCCAT"x1000; print "\n"' > testcase.txt 
$ t_coffee testcase.txt
... [you should run out of memory soon]

So, how can I change the behaviour or kernel?
Please Cc: me in replies. Thanks.

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

Powered by blists - more mailing lists