linux-kernel - Re: Runaway process and oom-killer

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: <467008E9.7070902@nortel.com>
Date:	Wed, 13 Jun 2007 09:10:33 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Helge Hafting <helge.hafting@...el.hist.no>
CC:	John Sigler <linux.kernel@...e.fr>,
	Andrea Arcangeli <andrea@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: Runaway process and oom-killer

Helge Hafting wrote:

> My guess:
> Something needs memory but finds there is none to be had
> oom-killer is invoked and targets myapp.
> myapp takes some time to die. Particularly, the memory it uses
> isn't freed up instantly.

Has anyone considered actually bumping up the priority of the task being 
killed so that it gets to run and free up its resources in a timely manner?

We've done some experimenting with actually putting it in SCHED_RR and 
it seems to help (in the case of other busy SCHED_RR tasks on the 
system).  Admittedly we have an older kernel, so behaviour may be 
different now.

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/