From: Dexuan Cui <decui@microsoft.com>
To: Michal Hocko <mhocko@suse.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kirill Tkhai <ktkhai@virtuozzo.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Roman Gushchin <guro@fb.com>, Hugh Dickins <hughd@google.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Mel Gorman <mgorman@techsingularity.net>,
"dchinner@redhat.com" <dchinner@redhat.com>,
Greg Thelen <gthelen@google.com>,
Kuo-Hsin Yang <vovoy@chromium.org>
Subject: RE: isolate_lru_pages(): kernel BUG at mm/vmscan.c:1689!
Date: Thu, 2 May 2019 18:24:33 +0000 [thread overview]
Message-ID: <PU1P153MB0169009CB69F8365EBE6FC6EBF340@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20190502125514.GB29835@dhcp22.suse.cz>
> From: Michal Hocko <mhocko@suse.com>
> Sent: Thursday, May 2, 2019 5:55 AM
> > ...
> > So far I only hit the BUG once and I don't know how to reproduce it again, so
> this is just a FYI.
>
> ...
> Do you think it would be possible to setup a crash dump
> or apply the following debugging patch in case it reproduces?
> Michal Hocko
Now I applied the "dump_page(page);" and let's see if I'll hit the BUG again.
BTW, I'm developing some code to support hibernation for Linux VM running
on Hyper-V. I don't think my own change causes the BUG, as my change does not
touch the mm system or any file system code at all.
Thanks,
-- Dexuan
next prev parent reply other threads:[~2019-05-02 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 23:49 Dexuan Cui
2019-05-02 12:55 ` Michal Hocko
2019-05-02 18:24 ` Dexuan Cui [this message]
2019-05-08 10:33 ` Mel Gorman
2019-05-08 15:44 ` Dexuan Cui
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=PU1P153MB0169009CB69F8365EBE6FC6EBF340@PU1P153MB0169.APCP153.PROD.OUTLOOK.COM \
--to=decui@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=dchinner@redhat.com \
--cc=gthelen@google.com \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=ktkhai@virtuozzo.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vdavydov.dev@gmail.com \
--cc=vovoy@chromium.org \
/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