linux-kernel - Re: OOM notifications

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4718E24F.3060805@nortel.com>
Date:	Fri, 19 Oct 2007 10:58:55 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Samuel Tardieu <sam@...1149.net>
CC:	linux-kernel@...r.kernel.org
Subject: Re: OOM notifications

Samuel Tardieu wrote:
>>>>>>"Pavel" == Pavel Machek <pavel@....cz> writes:

> Pavel> That works okay on a PC, but try cellphone one day.
> 
> Pavel> You want management app to close the least used
> Pavel> application. You do not want _kernel_ to select "who to send
> Pavel> SIGTERM to".
> 
> That's why I would prefer that *all* processes receive the
> SIGDANGER/whatever (and of course ignore it by default). Only the
> management app would handle it in the case you describe and would
> select one or more applications to unload to free some memory.

It's still helpful to have two stages...one that all apps can listen to 
(and try to reduce their footprint if possible), and a second one that 
only the manager would handle (and would kill some suitable target). 
Finally, if all that fails then the kernel starts whacking things.

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