linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
* [patch] mm, oom: remove unnecessary exit_state check
@ 2014-07-29 23:39 David Rientjes
  2014-07-30 15:06 ` Oleg Nesterov
  0 siblings, 1 reply; 2+ messages in thread
From: David Rientjes @ 2014-07-29 23:39 UTC (permalink / raw)
  To: Andrew Morton; +Cc: Oleg Nesterov, linux-kernel, linux-mm

The oom killer scans each process and determines whether it is eligible for oom 
kill or whether the oom killer should abort because of concurrent memory 
freeing.  It will abort when an eligible process is found to have TIF_MEMDIE 
set, meaning it has already been oom killed and we're waiting for it to exit.

Processes with task->mm == NULL should not be considered because they are either 
kthreads or have already detached their memory and killing them would not lead 
to memory freeing.  That memory is only freed after exit_mm() has returned, 
however, and not when task->mm is first set to NULL.

Clear TIF_MEMDIE after exit_mm()'s mmput() so that an oom killed process is no 
longer considered for oom kill, but only until exit_mm() has returned.  This was 
fragile in the past because it relied on exit_notify() to be reached before no 
longer considering TIF_MEMDIE processes.

Signed-off-by: David Rientjes <rientjes@google.com>
---
 kernel/exit.c | 1 +
 mm/oom_kill.c | 2 --
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/kernel/exit.c b/kernel/exit.c
--- a/kernel/exit.c
+++ b/kernel/exit.c
@@ -455,6 +455,7 @@ static void exit_mm(struct task_struct * tsk)
 	task_unlock(tsk);
 	mm_update_next_owner(mm);
 	mmput(mm);
+	clear_thread_flag(TIF_MEMDIE);
 }
 
 /*
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
--- a/mm/oom_kill.c
+++ b/mm/oom_kill.c
@@ -258,8 +258,6 @@ enum oom_scan_t oom_scan_process_thread(struct task_struct *task,
 		unsigned long totalpages, const nodemask_t *nodemask,
 		bool force_kill)
 {
-	if (task->exit_state)
-		return OOM_SCAN_CONTINUE;
 	if (oom_unkillable_task(task, NULL, nodemask))
 		return OOM_SCAN_CONTINUE;
 

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [patch] mm, oom: remove unnecessary exit_state check
  2014-07-29 23:39 [patch] mm, oom: remove unnecessary exit_state check David Rientjes
@ 2014-07-30 15:06 ` Oleg Nesterov
  0 siblings, 0 replies; 2+ messages in thread
From: Oleg Nesterov @ 2014-07-30 15:06 UTC (permalink / raw)
  To: David Rientjes; +Cc: Andrew Morton, linux-kernel, linux-mm

On 07/29, David Rientjes wrote:
>
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -455,6 +455,7 @@ static void exit_mm(struct task_struct * tsk)
>  	task_unlock(tsk);
>  	mm_update_next_owner(mm);
>  	mmput(mm);
> +	clear_thread_flag(TIF_MEMDIE);
>  }
>  
>  /*
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -258,8 +258,6 @@ enum oom_scan_t oom_scan_process_thread(struct task_struct *task,
>  		unsigned long totalpages, const nodemask_t *nodemask,
>  		bool force_kill)
>  {
> -	if (task->exit_state)
> -		return OOM_SCAN_CONTINUE;

IIRC, this check was a workaround, to ensure that a oom-killed zombie
can't block oom-killer.

I think this patch can equally work.

Oleg.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-07-30 15:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-07-29 23:39 [patch] mm, oom: remove unnecessary exit_state check David Rientjes
2014-07-30 15:06 ` Oleg Nesterov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).