From: Sasha Levin <sasha.levin@oracle.com>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>, Mel Gorman <mgorman@suse.de>,
Dave Jones <davej@redhat.com>, linux-mm <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: mm: BUG in mempolicy's sp_insert
Date: Mon, 25 Feb 2013 20:54:56 -0500 [thread overview]
Message-ID: <512C15F0.6030907@oracle.com> (raw)
In-Reply-To: <CAHGf_=rur29gFs9R9AYeDwnbVBm3b3cOfAn2xyi=mQ+ZbgzEDA@mail.gmail.com>
On 02/25/2013 08:52 PM, KOSAKI Motohiro wrote:
> On Mon, Feb 25, 2013 at 8:30 AM, Sasha Levin <sasha.levin@oracle.com> wrote:
>> Hi all,
>>
>> While fuzzing with trinity inside a KVM tools guest running latest -next kernel,
>> I've stumbled on the following BUG:
>>
>> [13551.830090] ------------[ cut here ]------------
>> [13551.830090] kernel BUG at mm/mempolicy.c:2187!
>> [13551.830090] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>
> Unfortunately, I didn't reproduce this. I'll try it tonight.
I've actually managed to reproduce it again since then, so it's not a one time
fluke (which is a good sign a I guess).
It did require about an hour of fuzzing just mm with trinity.
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>
next prev parent reply other threads:[~2013-02-26 1:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 13:30 mm: BUG in mempolicy's sp_insert Sasha Levin
2013-02-26 1:52 ` KOSAKI Motohiro
2013-02-26 1:54 ` Sasha Levin [this message]
2013-02-26 11:39 ` Hillf Danton
2013-02-28 5:25 ` [PATCH 1/2] mempolicy: fix wrong sp_node insertion kosaki.motohiro
2013-02-28 5:25 ` [PATCH 2/2] mempolicy: fix typo kosaki.motohiro
2013-02-28 23:54 ` Andrew Morton
2013-03-01 1:28 ` KOSAKI Motohiro
2013-02-28 5:26 ` mm: BUG in mempolicy's sp_insert KOSAKI Motohiro
2013-02-28 6:53 ` Hillf Danton
2013-03-01 1:30 ` KOSAKI Motohiro
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=512C15F0.6030907@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).