From: Minchan Kim <minchan.kim@gmail.com>
To: David Rientjes <rientjes@google.com>
Cc: Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch -mmotm] oom: only oom kill exiting tasks with attached memory
Date: Tue, 9 Jun 2009 00:21:28 +0900 [thread overview]
Message-ID: <28c262360906080821v542bc573r496209402779d5c2@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.0906071617010.27806@chino.kir.corp.google.com>
Hi, David.
On Mon, Jun 8, 2009 at 8:18 AM, David Rientjes<rientjes@google.com> wrote:
> On Sun, 7 Jun 2009, Balbir Singh wrote:
>
>> Seems like a good change to make. Did you encounter this situation on
>> a real machine?
>>
>
> I did, as the result of the chosen task remaining in PF_EXITING state with
> a detached mm following a previous oom kill.
> --
Let me have a question.
If I understand your situation properly, you mean
Time order
t1 < t2 < t3 < t4.
t1 : oom kill A process - send signal. it doesn't destroy mm_struct yet.
t2 : destroy A's mm_struct but it is in task list.
t3 : It happens OOM, again. Process A is selected again since it still
remain in task list
t4 : Now A's mm_struct is destroyed => situation you said.
Is right ?
Do you turn on sysctl oom_kill_allocating_task ?
--
Kinds regards,
Minchan Kim
next prev parent reply other threads:[~2009-06-08 15:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 22:12 David Rientjes
2009-06-07 14:06 ` Rik van Riel
2009-06-07 14:12 ` Balbir Singh
2009-06-07 23:18 ` David Rientjes
2009-06-08 15:21 ` Minchan Kim [this message]
2009-06-08 1:08 ` 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=28c262360906080821v542bc573r496209402779d5c2@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
--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
all inboxes | Powered by JetHome®