From: Fengguang Wu <fengguang.wu@intel.com>
To: Hugh Dickins <hughd@google.com>
Cc: Sasha Levin <levinsasha928@gmail.com>,
Michel Lespinasse <walken@google.com>,
linux-mm@kvack.org, riel@redhat.com, peterz@infradead.org,
aarcange@redhat.com, daniel.santos@pobox.com,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Dave Jones <davej@redhat.com>, Jiri Slaby <jslaby@suse.cz>
Subject: Re: [PATCH 6/7] mm: add CONFIG_DEBUG_VM_RB build option
Date: Fri, 21 Sep 2012 06:31:06 +0800 [thread overview]
Message-ID: <20120920223106.GA10967@localhost> (raw)
In-Reply-To: <alpine.LSU.2.00.1209201520410.15904@eggly.anvils>
On Thu, Sep 20, 2012 at 03:27:11PM -0700, Hugh Dickins wrote:
> On Fri, 21 Sep 2012, Fengguang Wu wrote:
> > On Sat, Sep 15, 2012 at 11:26:23AM +0200, Sasha Levin wrote:
> > > On 09/15/2012 02:00 AM, Michel Lespinasse wrote:
> > > > All right. Hugh managed to reproduce the issue on his suse laptop, and
> > > > I came up with a fix.
> > > >
> > > > The problem was that in mremap, the new vma's vm_{start,end,pgoff}
> > > > fields need to be updated before calling anon_vma_clone() so that the
> > > > new vma will be properly indexed.
> > > >
> > > > Patch attached. I expect this should also explain Jiri's reported
> > > > failure involving splitting THP pages during mremap(), even though we
> > > > did not manage to reproduce that one.
> > >
> > > Initially I've stumbled on it by running trinity inside a KVM tools guest. fwiw,
> > > the guest is pretty custom and isn't based on suse.
> > >
> > > I re-ran tests with patch applied and looks like it fixed the issue, I haven't
> > > seen the warnings even though it runs for quite a while now.
> >
> > Not sure if it's the same problem you are talking about, but I got the
> > below warning and it's still happening in linux-next 20120920:
>
> It is (almost certainly) the same problem, for which Michel provided
> the fix earlier in this thread (some of us find we have to delete a
> " {" from the context at the end to get it to apply).
>
> That fix has gone into akpm's tree, but linux-next is still using an
> older rollup of akpm's tree.
Got it, thank you for the quick information!
Thanks,
Fengguang
> > [ 38.482925] scsi_nl_rcv_msg: discarding partial skb
> > [ 62.679879] ------------[ cut here ]------------
> > [ 62.680380] WARNING: at /c/kernel-tests/src/linux/mm/interval_tree.c:109 anon_vma_interval_tree_verify+0x33/0x80()
> > [ 62.681356] Pid: 195, comm: trinity-child0 Not tainted 3.6.0-rc6-next-20120918-08732-g3de9d1a #1
> > [ 62.682130] Call Trace:
> > [ 62.682356] [<ffffffff810c249f>] ? anon_vma_interval_tree_verify+0x33/0x80
> > [ 62.682968] [<ffffffff81044356>] warn_slowpath_common+0x5d/0x74
> > [ 62.683577] [<ffffffff81044424>] warn_slowpath_null+0x15/0x19
> > [ 62.684098] [<ffffffff810c249f>] anon_vma_interval_tree_verify+0x33/0x80
> > [ 62.684714] [<ffffffff810ca57c>] validate_mm+0x32/0x15b
> > [ 62.685202] [<ffffffff810ca767>] vma_link+0x95/0xa4
> > [ 62.685637] [<ffffffff810cbc31>] copy_vma+0x1c7/0x1fe
> > [ 62.686168] [<ffffffff810cdd50>] move_vma+0x90/0x1ef
> > [ 62.686614] [<ffffffff810ce250>] sys_mremap+0x3a1/0x429
> > [ 62.687094] [<ffffffff813caafe>] ? trace_hardirqs_on_thunk+0x3a/0x3f
> > [ 62.687670] [<ffffffff81b505b9>] system_call_fastpath+0x16/0x1b
> >
> > Bisected down to
> >
> > commit cb58d445d2ec3a06f313e29d6f6af5bef6c9e43c
> > Author: Michel Lespinasse <walken@google.com>
> > Date: Thu Sep 13 10:58:56 2012 +1000
> >
> > mm: add CONFIG_DEBUG_VM_RB build option
> >
> > Thanks,
> > Fengguang
--
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:[~2012-09-20 22:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-04 9:20 [PATCH 0/7] use interval trees for anon rmap Michel Lespinasse
2012-09-04 9:20 ` [PATCH 1/7] mm: interval tree updates Michel Lespinasse
2012-09-07 22:13 ` Andrew Morton
2012-09-07 22:29 ` Michel Lespinasse
2012-09-07 22:55 ` Andrew Morton
2012-09-07 23:26 ` Michel Lespinasse
2012-09-08 4:45 ` Hillf Danton
2012-09-07 23:26 ` Michel Lespinasse
2012-09-04 9:20 ` [PATCH 2/7] mm: fix potential anon_vma locking issue in mprotect() Michel Lespinasse
2012-09-04 14:27 ` Andrea Arcangeli
2012-09-04 21:53 ` Michel Lespinasse
2012-09-04 22:16 ` Andrea Arcangeli
2012-09-05 0:45 ` Michel Lespinasse
2012-09-04 9:20 ` [PATCH 3/7] mm anon rmap: remove anon_vma_moveto_tail Michel Lespinasse
2012-09-04 9:20 ` [PATCH 4/7] mm anon rmap: replace same_anon_vma linked list with an interval tree Michel Lespinasse
2012-09-05 0:51 ` Michel Lespinasse
2012-09-04 9:20 ` [PATCH 5/7] mm rmap: remove vma_address check for address inside vma Michel Lespinasse
2012-09-04 9:20 ` [PATCH 6/7] mm: add CONFIG_DEBUG_VM_RB build option Michel Lespinasse
2012-09-14 22:14 ` Sasha Levin
2012-09-14 22:40 ` Sasha Levin
2012-09-14 22:46 ` Michel Lespinasse
2012-09-15 0:00 ` Michel Lespinasse
2012-09-15 7:52 ` Jiri Slaby
2012-09-16 19:07 ` Hugh Dickins
2012-09-22 7:19 ` Jiri Slaby
2012-09-15 9:26 ` Sasha Levin
2012-09-20 21:39 ` Fengguang Wu
2012-09-20 22:27 ` Hugh Dickins
2012-09-20 22:31 ` Fengguang Wu [this message]
2012-09-04 9:20 ` [PATCH 7/7] mm: avoid taking rmap locks in move_ptes() 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=20120920223106.GA10967@localhost \
--to=fengguang.wu@intel.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.santos@pobox.com \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=jslaby@suse.cz \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).