lkml.org 
[lkml]   [2014]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 3/4] OOM, PM: OOM killed task shouldn't escape PM suspend
On Thu, Nov 06, 2014 at 05:01:58PM +0100, Michal Hocko wrote:
> Yes, OOM killer simply kicks the process sets TIF_MEMDIE and terminates.
> That will release the read_lock, allow this to take the write lock and
> check whether it the current has been killed without any races.
> OOM killer doesn't wait for the killed task. The allocation is retried.
>
> Does this explain your concern?

Draining oom killer then doesn't mean anything, no? OOM killer may
have been disabled and drained but the killed tasks might wake up
after the PM freezer considers them to be frozen, right? What am I
missing?

--
tejun


\
 
 \ /
  Last update: 2014-11-06 17:21    [W:0.504 / U:1.916 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site