linux-kernel - Re: OOM (HighMem) on linux 2.6.24.2

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: <200804010431.11271.vda.linux@googlemail.com>
Date:	Tue, 1 Apr 2008 04:31:11 +0200
From:	Denys Vlasenko <vda.linux@...glemail.com>
To:	Kevin Shanahan <kmshanah@...b.org.au>
Cc:	Peter Zijlstra <peterz@...radead.org>, linux-kernel@...r.kernel.org
Subject: Re: OOM (HighMem) on linux 2.6.24.2

On Thursday 20 March 2008 11:04, Kevin Shanahan wrote:
> Feb 28 06:32:20 hermes kernel: 5313 pages slab
> Feb 28 06:32:20 hermes kernel: 2632 pages pagetables
> Feb 28 06:32:20 hermes kernel: Out of memory: kill process 24013 (apache2) score 22070 or a child
> Feb 28 06:32:20 hermes kernel: Killed process 24013 (apache2)
> 
> Looks like the HighMem low watermark was hit again (though I've no idea
> if that's actually significant).

I kno that people routinely forget to do that, but
at least for purely paranoid reasons you are better
to run all daemons with setrlimit'ed memory size.
At least all daemons which you cannot reasonably
trust to be 100% leak-free and to have bounded
peak memory usage.

This way, only leaking saemon will die (and you will easily see
which one) instead of entire system.
--
vda
--
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/