From: Bob Liu <lliubbo@gmail.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Andrea Arcangeli <aarcange@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: mm: kernel BUG at mm/huge_memory.c:2785!
Date: Wed, 5 Mar 2014 11:16:41 +0800 [thread overview]
Message-ID: <CAA_GA1c02iSmkmCLHFkrK4b4W+JppZ4CSMUJ-Wn1rCs-c=dV6g@mail.gmail.com> (raw)
In-Reply-To: <20140227150313.3BA27E0098@blue.fi.intel.com>
On Thu, Feb 27, 2014 at 11:03 PM, Kirill A. Shutemov
<kirill.shutemov@linux.intel.com> wrote:
> 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:
>>
>> [ 1428.146261] kernel BUG at mm/huge_memory.c:2785!
>
> Hm, interesting.
>
> It seems we either failed to split huge page on vma split or it
> materialized from under us. I don't see how it can happen:
>
> - it seems we do the right thing with vma_adjust_trans_huge() in
> __split_vma();
> - we hold ->mmap_sem all the way from vm_munmap(). At least I don't see
> a place where we could drop it;
>
Enable CONFIG_DEBUG_VM may show some useful information, at least we
can confirm weather rwsem_is_locked(&tlb->mm->mmap_sem) before
split_huge_page_pmd().
--
Regards,
--Bob
--
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:[~2014-03-05 3:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 13:35 Sasha Levin
2014-02-27 15:03 ` Kirill A. Shutemov
2014-03-04 23:57 ` Sasha Levin
2014-03-05 13:52 ` Kirill A. Shutemov
2014-03-06 4:44 ` Sasha Levin
2014-03-05 3:16 ` Bob Liu [this message]
2014-03-05 3:53 ` Sasha Levin
2014-03-07 1:32 ` Sasha Levin
2014-03-07 12:18 ` Kirill A. Shutemov
2014-03-14 20:42 ` 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='CAA_GA1c02iSmkmCLHFkrK4b4W+JppZ4CSMUJ-Wn1rCs-c=dV6g@mail.gmail.com' \
--to=lliubbo@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox