linux-kernel - Re: oom-killer with 27G free swap and overcommit

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

Date:	Tue, 28 Aug 2007 08:18:57 +0300
From:	Al Boldi <a1426z@...ab.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: oom-killer with 27G free swap and overcommit_memory=2

Patrick J. LoPresti wrote:
> My system is a SunFire x4100 (x86_64) with 16G of RAM and 32G of swap
> in a single partition.  I have an application which consumes a lot of
> memory, and after a few hours the oom-killer kills it.
> 
> This would not be surprising, except a) the machine still has 27G of
> free swap at the time; and b) it happens even when I set
> vm.overcommit_memory=2 (with overcommit_ratio=50).  It is
> time-consuming to reproduce, but consistent.
:
:
> 2) Is there any sysctl setting that might "avoid" this problem?  Or a
> way to change my application to avoid it?

Try setting the overcommit_ratio=0.


Thanks!

--
Al

-
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/