linux-kernel - Re: Out of memory management in embedded systems

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

Message-Id: <200710011625.47466.rgetz@blackfin.uclinux.org>
Date:	Mon, 1 Oct 2007 16:25:47 -0400
From:	Robin Getz <rgetz@...ckfin.uclinux.org>
To:	david@...g.hm
Cc:	"Bernd Eckenfels" <ecki@...a.inka.de>, linux-kernel@...r.kernel.org
Subject: Re: Out of memory management in embedded systems

On Mon 1 Oct 2007 12:27, david@...g.hm pondered:
> overcommit by default is optimistic that if the program requesting the 
> memory actually tries to use it there will be enough (both the fork-exec
> situation and the copy-on-write memory of real forks mean that the
> system ends up useing much less memory then is theoretically allocated).
> 
> switching it to be pessimistic (overcommit 2 IIRC) means that the OOM 
> handler will never kick in, but it means that programs will be told that
> there isn't any memory when there really is enough for the program to 
> work.

I have set it to 2, and still get the OOM if I malloc too much... I never get 
a null back from malloc, no matter what I try.

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