lkml.org 
[lkml]   [2007]   [Jun]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [patch] cpusets: do not allow TIF_MEMDIE tasks to allocate globally
On Tue, 5 Jun 2007, Christoph Lameter wrote:

> Hmmmm... But we have sent it a SIGKILL. If the process is following
> conventions then it is exiting. Of course the process could be abusing the
> system and attempting to OOM the whole system as an act of revenge for
> being killed but isnt this a bit far fetched?
>

It's not abusing the system because it was killed, it was killed because
it was abusing the system and attempted to mlock more memory than allowed
in its exclusive mems. So we OOM the task but it can continue mlock'ing
memory and intrude on the memory of other cpusets because of the
TIF_MEMDIE exception and our SIGKILL hasn't been handled yet.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-06-06 05:33    [W:0.164 / U:0.980 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site