Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1423098

Re: [PATCH 09/10] mm, oom_reaper: do not attempt to reap a task more than twice

From Oleg Nesterov <oleg@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH 09/10] mm, oom_reaper: do not attempt to reap a task more than twice
Date 2016-06-15 16:50 +0200
Message-ID <rKkiK-3Lp-9@gated-at.bofh.it> (permalink)
References <rI6MV-5RF-3@gated-at.bofh.it> <rI6MV-5RF-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 06/09, Michal Hocko wrote:
>
> @@ -556,8 +556,27 @@ static void oom_reap_task(struct task_struct *tsk)
>  		schedule_timeout_idle(HZ/10);
>  
>  	if (attempts > MAX_OOM_REAP_RETRIES) {
> +		struct task_struct *p;
> +
>  		pr_info("oom_reaper: unable to reap pid:%d (%s)\n",
>  				task_pid_nr(tsk), tsk->comm);
> +
> +		/*
> +		 * If we've already tried to reap this task in the past and
> +		 * failed it probably doesn't make much sense to try yet again
> +		 * so hide the mm from the oom killer so that it can move on
> +		 * to another task with a different mm struct.
> +		 */
> +		p = find_lock_task_mm(tsk);
> +		if (p) {
> +			if (test_and_set_bit(MMF_OOM_NOT_REAPABLE, &p->mm->flags)) {
> +				pr_info("oom_reaper: giving up pid:%d (%s)\n",
> +						task_pid_nr(tsk), tsk->comm);
> +				set_bit(MMF_OOM_REAPED, &p->mm->flags);

But why do we need MMF_OOM_NOT_REAPABLE? We set MMF_OOM_REAPED, oom_reap_task()
should not see this task again, at least too often.

Oleg.

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH 09/10] mm, oom_reaper: do not attempt to reap a task more  than twice Oleg Nesterov <oleg@redhat.com> - 2016-06-15 16:50 +0200
  Re: [PATCH 09/10] mm, oom_reaper: do not attempt to reap a task more  than twice Michal Hocko <mhocko@kernel.org> - 2016-06-16 08:30 +0200

csiph-web