From: Mel Gorman <mgorman@suse.de>
To: Jovi Zhangwei <jovi@cloudflare.com>
Cc: linux-kernel@vger.kernel.org, sasha.levin@oracle.com,
n-horiguchi@ah.jp.nec.com, akpm@linux-foundation.org,
hughd@google.com, linux-mm@kvack.org, vbabka@suse.cz,
rientjes@google.com
Subject: Re: kernel bug(VM_BUG_ON_PAGE) with 3.18.13 in mm/migrate.c
Date: Thu, 28 May 2015 13:00:15 +0100 [thread overview]
Message-ID: <20150528120015.GA26425@suse.de> (raw)
In-Reply-To: <CABPcSq+uMcDSBU1xt7oRqPXn-89ZpJmxK+C46M7rX7+Y7-x7iQ@mail.gmail.com>
On Wed, May 27, 2015 at 11:05:33AM -0700, Jovi Zhangwei wrote:
> Hi,
>
> I got below kernel bug error in our 3.18.13 stable kernel.
> "kernel BUG at mm/migrate.c:1661!"
>
> Source code:
>
> 1657 static int numamigrate_isolate_page(pg_data_t *pgdat, struct page *page)
> 1658 {
> 1659 int page_lru;
> 1660
> 1661 VM_BUG_ON_PAGE(compound_order(page) &&
> !PageTransHuge(page), page);
>
> It's easy to trigger the error by run tcpdump in our system.(not sure
> it will easily be reproduced in another system)
> "sudo tcpdump -i bond0.100 'tcp port 4242' -c 100000000000 -w 4242.pcap"
>
> Any comments for this bug would be great appreciated. thanks.
>
What sort of compound page is it? What sort of VMA is it in? hugetlbfs
pages should never be tagged for NUMA migrate and never enter this
path. Transparent huge pages are handled properly so I'm wondering
exactly what type of compound page this is and what mapped it into
userspace.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2015-05-28 12:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 18:05 kernel bug(VM_BUG_ON_PAGE) with 3.18.13 in mm/migrate.c Jovi Zhangwei
2015-05-27 18:42 ` Jovi Zhangwei
2015-05-28 12:00 ` Mel Gorman [this message]
2015-05-28 18:38 ` Jovi Zhangwei
2015-05-31 1:39 ` Jovi Zhangwei
2015-06-02 7:19 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2015-05-26 23:44 Jovi Zhangwei
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=20150528120015.GA26425@suse.de \
--to=mgorman@suse.de \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=jovi@cloudflare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=rientjes@google.com \
--cc=sasha.levin@oracle.com \
--cc=vbabka@suse.cz \
/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;
as well as URLs for NNTP newsgroup(s).