From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
khlebnikov@openvz.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: kernel BUG at include/linux/swapops.h:131!
Date: Wed, 18 Dec 2013 19:41:45 +0400 [thread overview]
Message-ID: <20131218154145.GW8167@moon> (raw)
In-Reply-To: <52B1C143.8080301@oracle.com>
On Wed, Dec 18, 2013 at 10:37:39AM -0500, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest
> -next kernel, I've stumbled on the following spew.
>
> The code is in zap_pte_range():
>
> if (!non_swap_entry(entry))
> rss[MM_SWAPENTS]--;
> else if (is_migration_entry(entry)) {
> struct page *page;
>
> page = migration_entry_to_page(entry); <==== HERE
>
> if (PageAnon(page))
> rss[MM_ANONPAGES]--;
> else
> rss[MM_FILEPAGES]--;
This I think is my issue, I'll take a look, thanks Sasha!
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
khlebnikov@openvz.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: kernel BUG at include/linux/swapops.h:131!
Date: Wed, 18 Dec 2013 19:41:45 +0400 [thread overview]
Message-ID: <20131218154145.GW8167@moon> (raw)
In-Reply-To: <52B1C143.8080301@oracle.com>
On Wed, Dec 18, 2013 at 10:37:39AM -0500, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running latest
> -next kernel, I've stumbled on the following spew.
>
> The code is in zap_pte_range():
>
> if (!non_swap_entry(entry))
> rss[MM_SWAPENTS]--;
> else if (is_migration_entry(entry)) {
> struct page *page;
>
> page = migration_entry_to_page(entry); <==== HERE
>
> if (PageAnon(page))
> rss[MM_ANONPAGES]--;
> else
> rss[MM_FILEPAGES]--;
This I think is my issue, I'll take a look, thanks Sasha!
next prev parent reply other threads:[~2013-12-18 15:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-18 15:37 mm: kernel BUG at include/linux/swapops.h:131! Sasha Levin
2013-12-18 15:37 ` Sasha Levin
2013-12-18 15:41 ` Cyrill Gorcunov [this message]
2013-12-18 15:41 ` Cyrill Gorcunov
2013-12-18 15:46 ` Cyrill Gorcunov
2013-12-18 15:46 ` Cyrill Gorcunov
2013-12-23 17:24 ` Sasha Levin
2013-12-23 17:24 ` Sasha Levin
2013-12-24 2:51 ` Joonsoo Kim
2013-12-24 2:51 ` Joonsoo Kim
2013-12-24 3:01 ` Sasha Levin
2013-12-24 3:01 ` Sasha Levin
2013-12-24 6:07 ` Joonsoo Kim
2013-12-24 6:07 ` Joonsoo Kim
2013-12-24 7:45 ` Joonsoo Kim
2013-12-24 7:45 ` Joonsoo Kim
2013-12-25 1:07 ` Wanpeng Li
2013-12-26 1:21 ` Bob Liu
2013-12-26 1:21 ` Bob Liu
2013-12-26 5:51 ` Konstantin Khlebnikov
2013-12-26 6:18 ` Konstantin Khlebnikov
2013-12-26 6:18 ` Konstantin Khlebnikov
2013-12-26 6:27 ` Wanpeng Li
2013-12-24 19:27 ` Sasha Levin
2013-12-24 19:27 ` Sasha Levin
2014-01-02 6:36 ` Bob Liu
2014-01-02 6:36 ` Bob Liu
2014-01-04 2:57 ` Sasha Levin
2014-01-04 2:57 ` Sasha Levin
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=20131218154145.GW8167@moon \
--to=gorcunov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=khlebnikov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sasha.levin@oracle.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.