[lkml]   [2016]   [Jun]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 10/10] mm, oom: hide mm which is shared with kthread or global init
Tetsuo Handa wrote:
> But this is not safe for CONFIG_MMU=y kernels as well.
> can_oom_reap == false means that oom_reap_task() will not be called.
> It is possible that the TIF_MEMDIE thread falls into
> atomic_read(&task->signal->oom_victims) > 0 && find_lock_task_mm(task) == NULL
> situation. We are still risking OOM livelock. We must somehow clear (or ignore)
> TIF_MEMDIE even if oom_reap_task() is not called.

Oops. mmput() from exit_mm() does not block in that case. So, we won't livelock here.

> Can't we apply now?

 \ /
  Last update: 2016-06-16 16:01    [W:0.083 / U:0.216 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site