linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "avagin@gmail.com" <avagin@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Andrey Vagin <avagin@openvz.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH rh6] mm: skip zombie in OOM-killer
Date: Sat, 05 Mar 2011 03:52:03 +0300	[thread overview]
Message-ID: <4D718933.1050106@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1103041541040.7795@chino.kir.corp.google.com>

On 03/05/2011 02:41 AM, David Rientjes wrote:
> On Sat, 5 Mar 2011, Andrey Vagin wrote:
>
>> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
>> index 7dcca55..2fc554e 100644
>> --- a/mm/oom_kill.c
>> +++ b/mm/oom_kill.c
>> @@ -311,7 +311,7 @@ static struct task_struct *select_bad_process(unsigned int *ppoints,
>>   		 * blocked waiting for another task which itself is waiting
>>   		 * for memory. Is there a better alternative?
>>   		 */
>> -		if (test_tsk_thread_flag(p, TIF_MEMDIE))
>> +		if (test_tsk_thread_flag(p, TIF_MEMDIE)&&  p->mm)
>>   			return ERR_PTR(-1UL);
>>
>>   		/*
>
> I think it would be better to just do
>
> 	if (!p->mm)
> 		continue;
>
> after the check for oom_unkillable_task() because everything that follows
> this really depends on p->mm being non-NULL to actually do anything
> useful.
Yes. You are right. Thank you.

  reply	other threads:[~2011-03-05  0:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-04 21:30 [PATCH rh6] mm: skip zombie in OOM-killer Andrey Vagin
2011-03-04 23:41 ` David Rientjes
2011-03-05  0:52   ` avagin [this message]
2011-03-06 11:20   ` KOSAKI Motohiro
2011-03-08  1:25 ` 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=4D718933.1050106@gmail.com \
    --to=avagin@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).