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
| ||
|
Date: Fri, 13 May 2016 15:34:52 +0200 From: Sebastian Frias <sf84@...oste.net> To: "Austin S. Hemmelgarn" <ahferroin7@...il.com>, Michal Hocko <mhocko@...nel.org> CC: Mason <slash.tmp@...e.fr>, linux-mm@...ck.org, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, LKML <linux-kernel@...r.kernel.org> Subject: Re: [PATCH] mm: add config option to select the initial overcommit mode Hi Austin, On 05/13/2016 03:11 PM, Austin S. Hemmelgarn wrote: > On 2016-05-13 08:39, Sebastian Frias wrote: >> >> My point is that it seems to be possible to deal with such conditions in a more controlled way, ie: a way that is less random and less abrupt. > There's an option for the OOM-killer to just kill the allocating task instead of using the scoring heuristic. This is about as deterministic as things can get though. By the way, why does it has to "kill" anything in that case? I mean, shouldn't it just tell the allocating task that there's not enough memory by letting malloc return NULL? Best regards, Sebastian
Powered by blists - more mailing lists