From: Andrew Morton <akpm@linux-foundation.org>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Wanpeng Li <liwanp@linux.vnet.ibm.com>,
Sasha Levin <sasha.levin@oracle.com>,
Hugh Dickins <hughd@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/rmap: fix BUG at rmap_walk
Date: Wed, 18 Dec 2013 17:04:29 -0800 [thread overview]
Message-ID: <20131218170429.0858bb069d51a469e8c237d8@linux-foundation.org> (raw)
In-Reply-To: <20131219005805.GA25161@lge.com>
On Thu, 19 Dec 2013 09:58:05 +0900 Joonsoo Kim <iamjoonsoo.kim@lge.com> wrote:
> On Wed, Dec 18, 2013 at 04:28:58PM -0800, Andrew Morton wrote:
> > On Thu, 19 Dec 2013 08:16:35 +0800 Wanpeng Li <liwanp@linux.vnet.ibm.com> wrote:
> >
> > > page_get_anon_vma() called in page_referenced_anon() will lock and
> > > increase the refcount of anon_vma, page won't be locked for anonymous
> > > page. This patch fix it by skip check anonymous page locked.
> > >
> > > [ 588.698828] kernel BUG at mm/rmap.c:1663!
> >
> > Why is all this suddenly happening. Did we change something, or did a
> > new test get added to trinity?
>
> It is my fault.
> I should remove this VM_BUG_ON() since rmap_walk() can be called
> without holding PageLock() in this case.
>
> I think that adding VM_BUG_ON() to each rmap_walk calllers is better
> than this patch, because, now, rmap_walk() is called by many places and
> each places has different contexts.
I don't think that putting the assertion into the caller makes a lot of
sense, particularly if that code just did a lock_page()! If a *callee*
needs PageLocked() then that callee should assert that the page is
locked. So
VM_BUG_ON(!PageLocked(page));
means "this code requires that the page be locked". And if that code
requires PageLocked(), there must be reasons for this. Let's also
include an explanation of those reasons.
--
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-12-19 1:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 0:16 [PATCH] mm/rmap: fix BUG at rmap_walk Wanpeng Li
2013-12-19 0:28 ` Andrew Morton
2013-12-19 0:41 ` Sasha Levin
2013-12-19 0:50 ` Andrew Morton
2013-12-19 1:30 ` Dave Jones
2013-12-19 0:56 ` Wanpeng Li
2013-12-19 0:58 ` Joonsoo Kim
2013-12-19 1:04 ` Andrew Morton [this message]
2013-12-19 1:12 ` Wanpeng Li
2013-12-19 1:14 ` Joonsoo Kim
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=20131218170429.0858bb069d51a469e8c237d8@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--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;
as well as URLs for NNTP newsgroup(s).