From: David Rientjes <rientjes@google.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: mhocko@suse.com, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] mm,oom_reaper: Check for MMF_OOM_SKIP before complain.
Date: Tue, 20 Mar 2018 13:49:59 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.20.1803201349270.167205@chino.kir.corp.google.com> (raw)
In-Reply-To: <201803202147.ICB09393.FFSJOOtHVQOFLM@I-love.SAKURA.ne.jp>
On Tue, 20 Mar 2018, Tetsuo Handa wrote:
> I got "oom_reaper: unable to reap pid:" messages when the victim thread
> was blocked inside free_pgtables() (which occurred after returning from
> unmap_vmas() and setting MMF_OOM_SKIP). We don't need to complain when
> exit_mmap() already set MMF_OOM_SKIP.
>
> [ 663.593821] Killed process 7558 (a.out) total-vm:4176kB, anon-rss:84kB, file-rss:0kB, shmem-rss:0kB
> [ 664.684801] oom_reaper: unable to reap pid:7558 (a.out)
> [ 664.892292] a.out D13272 7558 6931 0x00100084
> [ 664.895765] Call Trace:
> [ 664.897574] ? __schedule+0x25f/0x780
> [ 664.900099] schedule+0x2d/0x80
> [ 664.902260] rwsem_down_write_failed+0x2bb/0x440
> [ 664.905249] ? rwsem_down_write_failed+0x55/0x440
> [ 664.908335] ? free_pgd_range+0x569/0x5e0
> [ 664.911145] call_rwsem_down_write_failed+0x13/0x20
> [ 664.914121] down_write+0x49/0x60
> [ 664.916519] ? unlink_file_vma+0x28/0x50
> [ 664.919255] unlink_file_vma+0x28/0x50
> [ 664.922234] free_pgtables+0x36/0x100
> [ 664.924797] exit_mmap+0xbb/0x180
> [ 664.927220] mmput+0x50/0x110
> [ 664.929504] copy_process.part.41+0xb61/0x1fe0
> [ 664.932448] ? _do_fork+0xe6/0x560
> [ 664.934902] ? _do_fork+0xe6/0x560
> [ 664.937361] _do_fork+0xe6/0x560
> [ 664.939742] ? syscall_trace_enter+0x1a9/0x240
> [ 664.942693] ? retint_user+0x18/0x18
> [ 664.945309] ? page_fault+0x2f/0x50
> [ 664.947896] ? trace_hardirqs_on_caller+0x11f/0x1b0
> [ 664.951075] do_syscall_64+0x74/0x230
> [ 664.953747] entry_SYSCALL_64_after_hwframe+0x42/0xb7
>
> Signed-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
> Cc: Michal Hocko <mhocko@suse.com>
> Cc: David Rientjes <rientjes@google.com>
Acked-by: David Rientjes <rientjes@google.com>
But you'll need to send it to akpm.
next prev parent reply other threads:[~2018-03-20 20:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 11:57 [PATCH 1/2] mm,oom_reaper: Show trace of unable to reap victim thread Tetsuo Handa
2018-03-20 11:57 ` [PATCH 2/2] mm,oom_reaper: Correct MAX_OOM_REAP_RETRIES'th attempt Tetsuo Handa
2018-03-20 12:12 ` Michal Hocko
2018-03-20 12:37 ` Tetsuo Handa
2018-03-20 12:47 ` [PATCH 2/2] mm,oom_reaper: Check for MMF_OOM_SKIP before complain Tetsuo Handa
2018-03-20 20:49 ` David Rientjes [this message]
2018-03-22 10:46 ` [PATCH] " Tetsuo Handa
2018-03-22 11:59 ` Michal Hocko
2018-03-20 13:24 ` [PATCH 2/2] mm,oom_reaper: Correct MAX_OOM_REAP_RETRIES'th attempt Michal Hocko
2018-03-20 13:37 ` Tetsuo Handa
2018-03-20 13:44 ` Michal Hocko
2018-03-20 12:28 ` [PATCH 1/2] mm,oom_reaper: Show trace of unable to reap victim thread Michal Hocko
2018-03-20 12:52 ` Tetsuo Handa
2018-03-20 13:19 ` Michal Hocko
2018-03-20 13:30 ` Tetsuo Handa
2018-03-20 13:34 ` Michal Hocko
2018-03-20 13:50 ` Tetsuo Handa
2018-03-20 14:10 ` Michal Hocko
2018-03-20 14:20 ` Tetsuo Handa
2018-03-20 20:46 ` 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=alpine.DEB.2.20.1803201349270.167205@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
/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.