All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
To: David Rientjes <rientjes@google.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] mm, oom: dump stack of victim when reaping failed
Date: Thu, 16 Jan 2020 06:09:57 +0900	[thread overview]
Message-ID: <84fddb8e-a23b-e970-c8e9-74aa2fe2716d@i-love.sakura.ne.jp> (raw)
In-Reply-To: <alpine.DEB.2.21.2001151223040.13588@chino.kir.corp.google.com>

On 2020/01/16 5:27, David Rientjes wrote:
> I'm 
> currently tracking a stall in oom reaping where the victim doesn't always 
> have a lock held so we don't know where it's at in the kernel; I'm hoping 
> that a stack for the thread group leader will at least shed some light on 
> it.
> 

This change was already proposed at
https://lore.kernel.org/linux-mm/20180320122818.GL23100@dhcp22.suse.cz/ .

And according to that proposal, it is likely i_mmap_lock_write() in dup_mmap()
in copy_process(). We tried to make that lock killable but we gave it up
because nobody knows whether it is safe to do make it killable.

  reply	other threads:[~2020-01-15 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 23:20 [patch] mm, oom: dump stack of victim when reaping failed David Rientjes
2020-01-14 23:20 ` David Rientjes
2020-01-15  8:43 ` Michal Hocko
2020-01-15  9:18   ` Tetsuo Handa
2020-01-15 20:27     ` David Rientjes
2020-01-15 20:27       ` David Rientjes
2020-01-15 21:09       ` Tetsuo Handa [this message]
2020-01-16 21:05         ` David Rientjes
2020-01-16 21:05           ` David Rientjes

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=84fddb8e-a23b-e970-c8e9-74aa2fe2716d@i-love.sakura.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.