linux-kernel - PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

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]

Message-ID: <AANLkTimAF1zxXlnEavXSnlKTkQgGD0u9UqCtUVT_r9jV@mail.gmail.com>
Date:	Fri, 14 May 2010 22:53:51 +1000
From:	dave b <db.pub.mail@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: PROBLEM: oom killer and swap weirdness on 2.6.3* kernels

In 2.6.3* kernels (test case was performed on the 2.6.33.3 kernel)
when physical memory runs out and there is a large swap partition -
the system completely stalls.

I noticed that when running debian lenny using dm-crypt  with
encrypted / and swap with a  2.6.33.3 kernel (and all of the 2.6.3*
series iirc) when all physical memory is used (swapiness was left at
the default 60) the system hangs and does not respond. It can resume
normal operation some time later - however it seems to take a *very*
long time for the oom killer to come in. Obviously with swapoff this
doesn't happen - the oom killer comes in and does its job.

free -m
             total       used       free     shared    buffers     cached
Mem:          1980       1101        879          0         58        201
-/+ buffers/cache:        840       1139
Swap:        24943          0      24943

My simple test case is

dd if=/dev/zero of=/tmp/stall
and wait till /tmp fills...
--
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/