[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.1004081610020.3558@i5.linux-foundation.org>
Date: Thu, 8 Apr 2010 16:16:23 -0700 (PDT)
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Borislav Petkov <bp@...en8.de>
cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Rik van Riel <riel@...hat.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Minchan Kim <minchan.kim@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lee Schermerhorn <Lee.Schermerhorn@...com>,
Nick Piggin <npiggin@...e.de>,
Andrea Arcangeli <aarcange@...hat.com>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
sgunderson@...foot.com, hannes@...xchg.org
Subject: Re: [PATCH -v2] rmap: make anon_vma_prepare link in all the anon_vmas
of a mergeable VMA
On Thu, 8 Apr 2010, Borislav Petkov wrote:
>
> And this happens quite often - I changed the WARN_ONCE to WARN and can't
> start kvm, iceowl (mozilla calendar) and the console-kit-daemon craps up
> upon boot too:
Hmm. I tried console-kit-daemon, which I had installed, but didn't get
anything like that. Probably some setup difference.
I also went through every user of 'vm_area_cachep', and saw nothing
suspicious at least for the mmu case (I didn't check the nommu.c code). I
must have missed something.
One thing you could do is to add some more debugging info when that "no
anon_vma" warning happens. In particular, if you still have the SLUB
debugging on, you could try to do that
page = virt_to_head_page(vma);
object_err(vm_area_cachep, page, (void *)vma, "NULL anon_vma");
and it should give you _which_ routine did the kmem_cache_alloc() for the
vma that doesn't have an anon_vma.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists