From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: mhocko@kernel.org, mikhail.v.gavrilov@gmail.com
Cc: linux-mm@kvack.org, kvm@vger.kernel.org, kirill@shutemov.name
Subject: Re: KVM hang after OOM
Date: Tue, 20 Mar 2018 21:20:30 +0900 [thread overview]
Message-ID: <201803202120.FDI17671.VQMLOFJFOStHFO@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20180320065339.GA23100@dhcp22.suse.cz>
Michal Hocko wrote:
> On Mon 19-03-18 21:23:12, Mikhail Gavrilov wrote:
> > using swap actively.
> > But I'm already satisfied with proposed patch.
> >
> > I am attached dmesg when I triggering OOM three times. And every time
> > after it system survived.
> > I think this patch should be merged in mainline.
>
> Could you be more specific what is _this_ patch, please?
I think it is
"[PATCH] mm/thp: Do not wait for lock_page() in deferred_split_scan()".
Unless the problem is something like commit 0b1d647a02c5a1b6
("[PATCH] dm: work around mempool_alloc, bio_alloc_bioset deadlocks"),
there should be no need to use io_schedule_timeout().
Mikhail, can you test with only
"[PATCH] mm/thp: Do not wait for lock_page() in deferred_split_scan()" and
"[PATCHv2] mm/shmem: Do not wait for lock_page() in shmem_unused_huge_shrink()"
applied? Because the last dmesg.txt was using io_schedule_timeout()...
next prev parent reply other threads:[~2018-03-20 12:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-11 18:11 KVM hang after OOM Mikhail Gavrilov
2018-03-12 9:00 ` Kirill A. Shutemov
2018-03-12 18:56 ` Mikhail Gavrilov
2018-03-13 12:22 ` Tetsuo Handa
2018-03-15 12:34 ` Michal Hocko
2018-03-15 12:37 ` Michal Hocko
2018-03-12 10:22 ` Tetsuo Handa
2018-03-15 11:56 ` Tetsuo Handa
2018-03-15 20:10 ` Mikhail Gavrilov
2018-03-17 3:13 ` Tetsuo Handa
2018-03-19 16:23 ` Mikhail Gavrilov
2018-03-20 6:53 ` Michal Hocko
2018-03-20 12:20 ` Tetsuo Handa [this message]
[not found] ` <CABXGCsNBEpVoMzrhyNLKhzNxPs=9a+Z+2aUxJ8WtZ8gE+=OGSA@mail.gmail.com>
2018-03-22 8:39 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2018-03-11 16:50 Mikhail Gavrilov
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=201803202120.FDI17671.VQMLOFJFOStHFO@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=kirill@shutemov.name \
--cc=kvm@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mikhail.v.gavrilov@gmail.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.