linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Bob Liu <bob.liu@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Michel Lespinasse <walken@google.com>,
	npiggin@suse.de, kosaki.motohiro@jp.fujitsu.com, riel@redhat.com
Subject: Re: mm: kernel BUG at mm/mlock.c:82!
Date: Tue, 17 Dec 2013 16:26:57 +0800	[thread overview]
Message-ID: <52b00ae4.a377b60a.1c68.ffffe284SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <52AFF35E.7000908@oracle.com>

Hi Sasha,
On Tue, Dec 17, 2013 at 01:46:54AM -0500, Sasha Levin wrote:
>On 12/17/2013 12:39 AM, Bob Liu wrote:
>>cc'd more people.
>>
>>On 12/17/2013 09:04 AM, 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.
>>>
>>>Codewise, it's pretty straightforward. In try_to_unmap_cluster():
>>>
>>>                 page = vm_normal_page(vma, address, *pte);
>>>                 BUG_ON(!page || PageAnon(page));
>>>
>>>                 if (locked_vma) {
>>>                         mlock_vma_page(page);   /* no-op if already
>>>mlocked */
>>>                         if (page == check_page)
>>>                                 ret = SWAP_MLOCK;
>>>                         continue;       /* don't unmap */
>>>                 }
>>>
>>>And the BUG triggers once we see that 'page' isn't locked.
>>>
>>
>>Yes, I didn't see any place locked the corresponding page in
>>try_to_unmap_cluster().
>>
>>I'm afraid adding lock_page() over there may cause potential deadlock.
>>How about just remove the BUG_ON() in mlock_vma_page()?
>
>Welp, it's been there for 5 years now - there should be a good reason to justify removing it.
>

Page should be locked before invoke try_to_unmap(), this check can't be removed 
since this bug is just triggered by confirm !check page hold page lock in virtual 
scan during nolinear VMAs pages aging. Avoid to confirm !check page hold page 
lock is acceptable.

Regards,
Wanpeng Li 

>
>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>

--
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>

  reply	other threads:[~2013-12-17  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-17  1:04 Sasha Levin
2013-12-17  5:39 ` Bob Liu
2013-12-17  6:46   ` Sasha Levin
2013-12-17  8:26     ` Wanpeng Li [this message]
2013-12-17 16:32       ` Motohiro Kosaki
2013-12-18  2:02         ` Wanpeng Li
2013-12-18  2:17           ` Bob Liu
2013-12-18  9:21           ` Vlastimil Babka
     [not found]         ` <20131218020239.GA16603@hacker.(null)>
2013-12-18 19:27           ` Motohiro Kosaki
2013-12-17  8:12 ` Wanpeng Li

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=52b00ae4.a377b60a.1c68.ffffe284SMTPIN_ADDED_BROKEN@mx.google.com \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bob.liu@oracle.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=npiggin@suse.de \
    --cc=riel@redhat.com \
    --cc=sasha.levin@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox