linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org
Subject: Re: [patch] oom: avoid killing kthreads if they assume the oom killed thread's mm
Date: Tue, 26 Jul 2011 17:27:24 +0200	[thread overview]
Message-ID: <20110726152724.GE17958@tiehlicka.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.1107251711460.26480@chino.kir.corp.google.com>

On Mon 25-07-11 17:12:37, David Rientjes wrote:
> After selecting a task to kill, the oom killer iterates all processes and
> kills all other threads that share the same mm_struct in different thread
> groups.  It would not otherwise be helpful to kill a thread if its memory
> would not be subsequently freed.
> 
> A kernel thread, however, may assume a user thread's mm by using
> use_mm().  This is only temporary and should not result in sending a
> SIGKILL to that kthread.

Good catch. Have you ever seen this happening?

> 
> This patch ensures that only user threads and not kthreads are sent a
> SIGKILL if they share the same mm_struct as the oom killed task.
> 
> Signed-off-by: David Rientjes <rientjes@google.com>

Reviewed-by: Michal Hocko <mhocko@suse.cz>
> ---
>  mm/oom_kill.c |    5 +++--
>  1 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -433,7 +433,7 @@ static int oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
>  	task_unlock(p);
>  
>  	/*
> -	 * Kill all processes sharing p->mm in other thread groups, if any.
> +	 * Kill all user processes sharing p->mm in other thread groups, if any.
>  	 * They don't get access to memory reserves or a higher scheduler
>  	 * priority, though, to avoid depletion of all memory or task
>  	 * starvation.  This prevents mm->mmap_sem livelock when an oom killed
> @@ -443,7 +443,8 @@ static int oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
>  	 * signal.
>  	 */
>  	for_each_process(q)
> -		if (q->mm == mm && !same_thread_group(q, p)) {
> +		if (q->mm == mm && !same_thread_group(q, p) &&
> +		    !(q->flags & PF_KTHREAD)) {
>  			task_lock(q);	/* Protect ->comm from prctl() */
>  			pr_err("Kill process %d (%s) sharing same memory\n",
>  				task_pid_nr(q), q->comm);
> 

-- 
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9    
Czech Republic

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-07-26 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26  0:12 David Rientjes
2011-07-26 15:27 ` Michal Hocko [this message]
2011-07-26 22:05   ` David Rientjes
2011-07-27  7:59     ` Michal Hocko
2011-07-27  0:35 ` KOSAKI Motohiro

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110726152724.GE17958@tiehlicka.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=rientjes@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox