linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, oleg@redhat.com,
	rientjes@google.com, vdavydov@parallels.com, mst@redhat.com
Subject: Re: [PATCH 5/8] mm,oom_reaper: Make OOM reaper use list of mm_struct.
Date: Wed, 13 Jul 2016 09:48:37 +0200	[thread overview]
Message-ID: <20160713074837.GA28723@dhcp22.suse.cz> (raw)
In-Reply-To: <201607130042.FFE34886.FtJVOLOFMHQOSF@I-love.SAKURA.ne.jp>

On Wed 13-07-16 00:42:51, Tetsuo Handa wrote:
> Michal Hocko wrote:
> > On Tue 12-07-16 22:29:20, Tetsuo Handa wrote:
[...]
> > > Since later patch in the series will change oom_scan_process_thread() not
> > > to depend on atomic_read(&task->signal->oom_victims) != 0 &&
> > > find_lock_task_mm(task) != NULL, this patch removes exit_oom_victim()
> > > on remote thread.
> > 
> > I have already suggested doing this in a separate patch. Because
> > dropping exit_oom_victim has other side effectes (namely for
> > oom_killer_disable convergence guarantee).
> 
> You can apply
> http://lkml.kernel.org/r/1467365190-24640-3-git-send-email-mhocko@kernel.org
> at this point.

I would still prefer if exit_oom_victim was done in a separate patch.
Unless you have a strong reason to do it in this patch. I plan to rework
the above to remove exit_oom_victim along with the oom_killer_disable
change.

> > Also I would suggest doing set_bit(MMF_OOM_REAPED) from exit_oom_mm and
> > (in a follow up patch) rename it to MMF_SKIP_OOM_MM.
> > 
> > I haven't spotted any other issues.
> > 
> Oops. Please fold below fix into
> "[PATCH 5/8] mm,oom_reaper: Make OOM reaper use list of mm_struct.".
> 
> >From ae051fb92b285c0dc4ebc4953fadc755b1ae8a31 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Date: Wed, 13 Jul 2016 00:24:32 +0900
> Subject: [PATCH] mm,oom_reaper: Close race on exit_oom_mm().
> 
> Previous patch forgot to take a reference on mm, for __mmput() from
> mmput() from exit_mm() can drop mm->mm_count till 0 before the OOM
> reaper calls exit_oom_mm().

I have missed that as well. Please fold this in.

> 
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> ---
>  mm/oom_kill.c | 13 ++++++++-----
>  1 file changed, 8 insertions(+), 5 deletions(-)
> 
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> index 715f77d..4c8b686 100644
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -626,21 +626,24 @@ static int oom_reaper(void *unused)
>  		if (!list_empty(&oom_mm_list)) {
>  			mm = list_first_entry(&oom_mm_list, struct mm_struct,
>  					      oom_mm.list);
> -			victim = mm->oom_mm.victim;
>  			/*
> -			 * Take a reference on current victim thread in case
> -			 * oom_reap_task() raced with mark_oom_victim() by
> -			 * other threads sharing this mm.
> +			 * Take references on mm and victim in case
> +			 * oom_reap_task() raced with mark_oom_victim() or
> +			 * __mmput().
>  			 */
> +			atomic_inc(&mm->mm_count);
> +			victim = mm->oom_mm.victim;
>  			get_task_struct(victim);
>  		}
>  		spin_unlock(&oom_mm_lock);
>  		if (!mm)
>  			continue;
>  		oom_reap_task(victim, mm);
> -		put_task_struct(victim);
>  		/* Drop references taken by mark_oom_victim() */
>  		exit_oom_mm(mm);
> +		/* Drop references taken above. */
> +		put_task_struct(victim);
> +		mmdrop(mm);
>  	}
>  
>  	return 0;
> -- 
> 1.8.3.1
> 
> --
> 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>

-- 
Michal Hocko
SUSE Labs

--
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>

  reply	other threads:[~2016-07-13  7:48 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-12 13:29 [PATCH v3 0/8] Change OOM killer to use list of mm_struct Tetsuo Handa
2016-07-12 13:29 ` [PATCH 1/8] mm,oom_reaper: Reduce find_lock_task_mm() usage Tetsuo Handa
2016-07-12 13:29 ` [PATCH 2/8] mm,oom_reaper: Do not attempt to reap a task twice Tetsuo Handa
2016-07-12 14:19   ` Michal Hocko
2016-07-12 13:29 ` [PATCH 3/8] mm,oom: Use list of mm_struct used by OOM victims Tetsuo Handa
2016-07-12 14:28   ` Michal Hocko
2016-07-12 13:29 ` [PATCH 4/8] mm,oom: Close oom_has_pending_mm race Tetsuo Handa
2016-07-12 14:36   ` Michal Hocko
2016-07-12 13:29 ` [PATCH 5/8] mm,oom_reaper: Make OOM reaper use list of mm_struct Tetsuo Handa
2016-07-12 14:51   ` Michal Hocko
2016-07-12 15:42     ` Tetsuo Handa
2016-07-13  7:48       ` Michal Hocko [this message]
2016-07-12 13:29 ` [PATCH 6/8] mm,oom: Remove OOM_SCAN_ABORT case and signal_struct->oom_victims Tetsuo Handa
2016-07-12 13:29 ` [PATCH 7/8] mm,oom: Stop clearing TIF_MEMDIE on remote thread Tetsuo Handa
2016-07-12 14:53   ` Michal Hocko
2016-07-12 15:45     ` Tetsuo Handa
2016-07-13  8:13       ` Michal Hocko
2016-07-12 13:29 ` [PATCH 8/8] oom_reaper: Revert "oom_reaper: close race with exiting task" Tetsuo Handa
2016-07-12 14:56   ` Michal Hocko
2016-07-21 11:21 ` [PATCH v3 0/8] Change OOM killer to use list of mm_struct Michal Hocko
2016-07-22 11:09   ` Tetsuo Handa
2016-07-22 12:05     ` Michal Hocko
2016-07-23  2:59       ` Tetsuo Handa
2016-07-25  8:48         ` Michal Hocko
2016-07-25 11:07           ` Tetsuo Handa
2016-07-25 11:21             ` Michal Hocko
2016-07-25 11:47               ` Tetsuo Handa
2016-07-25 11:59                 ` Michal Hocko
2016-07-25 14:02                   ` Tetsuo Handa
2016-07-25 14:17                     ` Michal Hocko
2016-07-25 21:40                       ` Tetsuo Handa
2016-07-26  7:52                         ` Michal Hocko

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=20160713074837.GA28723@dhcp22.suse.cz \
    --to=mhocko@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mst@redhat.com \
    --cc=oleg@redhat.com \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=rientjes@google.com \
    --cc=vdavydov@parallels.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;
as well as URLs for NNTP newsgroup(s).