From: Sasha Levin <sasha.levin@oracle.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Michel Lespinasse <walken@google.com>,
Rik van Riel <riel@redhat.com>, Vlastimil Babka <vbabka@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: mmap_sem lock assertion failure in __mlock_vma_pages_range
Date: Tue, 11 Mar 2014 18:20:42 -0400 [thread overview]
Message-ID: <531F8C3A.1040502@oracle.com> (raw)
In-Reply-To: <1394574323.2786.45.camel@buesod1.americas.hpqcorp.net>
On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
>> >On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
>>>> > >>Bingo! With the above patch:
>>>>> > >> >
>>>>> > >> >[ 243.565794] kernel BUG at mm/vmacache.c:76!
>>>>> > >> >[ 243.566720] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>>>>> > >> >[ 243.568048] Dumping ftrace buffer:
>>>>> > >> >[ 243.568740] (ftrace buffer empty)
>>>>> > >> >[ 243.569481] Modules linked in:
>>>>> > >> >[ 243.570203] CPU: 10 PID: 10073 Comm: trinity-c332 Tainted: G W 3.14.0-rc5-next-20140307-sasha-00010-g1f812cb-dirty #143
>>> > >and this is also part of the DEBUG_PAGEALLOC + trinity combo! I suspect
>>> > >the root cause it the same as Fengguang's report.
>> >
>> >The BUG still happens without DEBUG_PAGEALLOC.
> Any idea what trinity itself is doing?
>
> Could you add the following, I just want to make sure the bug isn't
> being caused by an overflow:
Not hitting that WARN.
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: Sasha Levin <sasha.levin@oracle.com>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Michel Lespinasse <walken@google.com>,
Rik van Riel <riel@redhat.com>, Vlastimil Babka <vbabka@suse.cz>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: mmap_sem lock assertion failure in __mlock_vma_pages_range
Date: Tue, 11 Mar 2014 18:20:42 -0400 [thread overview]
Message-ID: <531F8C3A.1040502@oracle.com> (raw)
In-Reply-To: <1394574323.2786.45.camel@buesod1.americas.hpqcorp.net>
On 03/11/2014 05:45 PM, Davidlohr Bueso wrote:
> On Tue, 2014-03-11 at 17:02 -0400, Sasha Levin wrote:
>> >On 03/11/2014 04:47 PM, Davidlohr Bueso wrote:
>>>> > >>Bingo! With the above patch:
>>>>> > >> >
>>>>> > >> >[ 243.565794] kernel BUG at mm/vmacache.c:76!
>>>>> > >> >[ 243.566720] invalid opcode: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC
>>>>> > >> >[ 243.568048] Dumping ftrace buffer:
>>>>> > >> >[ 243.568740] (ftrace buffer empty)
>>>>> > >> >[ 243.569481] Modules linked in:
>>>>> > >> >[ 243.570203] CPU: 10 PID: 10073 Comm: trinity-c332 Tainted: G W 3.14.0-rc5-next-20140307-sasha-00010-g1f812cb-dirty #143
>>> > >and this is also part of the DEBUG_PAGEALLOC + trinity combo! I suspect
>>> > >the root cause it the same as Fengguang's report.
>> >
>> >The BUG still happens without DEBUG_PAGEALLOC.
> Any idea what trinity itself is doing?
>
> Could you add the following, I just want to make sure the bug isn't
> being caused by an overflow:
Not hitting that WARN.
Thanks,
Sasha
next prev parent reply other threads:[~2014-03-11 22:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 19:39 mm: mmap_sem lock assertion failure in __mlock_vma_pages_range Sasha Levin
2014-03-11 19:39 ` Sasha Levin
2014-03-11 20:07 ` Davidlohr Bueso
2014-03-11 20:07 ` Davidlohr Bueso
2014-03-11 20:12 ` Sasha Levin
2014-03-11 20:12 ` Sasha Levin
2014-03-11 20:21 ` Davidlohr Bueso
2014-03-11 20:21 ` Davidlohr Bueso
2014-03-11 20:30 ` Andrew Morton
2014-03-11 20:30 ` Andrew Morton
2014-03-11 20:35 ` Sasha Levin
2014-03-11 20:35 ` Sasha Levin
2014-03-11 20:42 ` Davidlohr Bueso
2014-03-11 20:42 ` Davidlohr Bueso
2014-03-11 20:45 ` Sasha Levin
2014-03-11 20:45 ` Sasha Levin
2014-03-11 20:47 ` Davidlohr Bueso
2014-03-11 20:47 ` Davidlohr Bueso
2014-03-11 20:57 ` Dave Jones
2014-03-11 20:57 ` Dave Jones
2014-03-11 21:02 ` Sasha Levin
2014-03-11 21:02 ` Sasha Levin
2014-03-11 21:45 ` Davidlohr Bueso
2014-03-11 21:45 ` Davidlohr Bueso
2014-03-11 22:20 ` Sasha Levin [this message]
2014-03-11 22:20 ` Sasha Levin
2014-03-13 19:00 ` Davidlohr Bueso
2014-03-13 19:00 ` Davidlohr Bueso
2014-03-13 20:57 ` Hugh Dickins
2014-03-13 20:57 ` Hugh Dickins
2014-03-14 16:14 ` Sasha Levin
2014-03-14 16:14 ` Sasha Levin
2014-03-11 21:59 ` Michel Lespinasse
2014-03-11 21:59 ` Michel Lespinasse
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=531F8C3A.1040502@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davidlohr@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=vbabka@suse.cz \
--cc=walken@google.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.