From: Andrew Morton <akpm@linux-foundation.org>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Sasha Levin <sasha.levin@oracle.com>,
Hugh Dickins <hughd@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.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 16:28:58 -0800 [thread overview]
Message-ID: <20131218162858.6ec808c067baf4644532e110@linux-foundation.org> (raw)
In-Reply-To: <1387412195-26498-1-git-send-email-liwanp@linux.vnet.ibm.com>
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?
> --- a/mm/rmap.c
> +++ b/mm/rmap.c
> @@ -1660,7 +1660,8 @@ done:
>
> int rmap_walk(struct page *page, struct rmap_walk_control *rwc)
> {
> - VM_BUG_ON(!PageLocked(page));
> + if (!PageAnon(page) || PageKsm(page))
> + VM_BUG_ON(!PageLocked(page));
>
> if (unlikely(PageKsm(page)))
> return rmap_walk_ksm(page, rwc);
Is there any reason why rmap_walk_ksm() and rmap_walk_file() *need*
PageLocked() whereas rmap_walk_anon() does not? If so, let's implement
it like this:
--- a/mm/rmap.c~a
+++ a/mm/rmap.c
@@ -1716,6 +1716,10 @@ static int rmap_walk_file(struct page *p
struct vm_area_struct *vma;
int ret = SWAP_AGAIN;
+ /*
+ * page must be locked because <reason goes here>
+ */
+ VM_BUG_ON(!PageLocked(page));
if (!mapping)
return ret;
mutex_lock(&mapping->i_mmap_mutex);
@@ -1737,8 +1741,6 @@ static int rmap_walk_file(struct page *p
int rmap_walk(struct page *page, int (*rmap_one)(struct page *,
struct vm_area_struct *, unsigned long, void *), void *arg)
{
- VM_BUG_ON(!PageLocked(page));
-
if (unlikely(PageKsm(page)))
return rmap_walk_ksm(page, rmap_one, arg);
else if (PageAnon(page))
--- a/mm/ksm.c~a
+++ a/mm/ksm.c
@@ -2006,6 +2006,9 @@ int rmap_walk_ksm(struct page *page, int
int search_new_forks = 0;
VM_BUG_ON(!PageKsm(page));
+ /*
+ * page must be locked because <reason goes here>
+ */
VM_BUG_ON(!PageLocked(page));
stable_node = page_stable_node(page);
Or if there is no reason why the page must be locked for
rmap_walk_ksm() and rmap_walk_file(), let's just remove rmap_walk()'s
VM_BUG_ON()? And rmap_walk_ksm()'s as well - it's duplicative anyway.
--
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 0:29 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 [this message]
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
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=20131218162858.6ec808c067baf4644532e110@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).