[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+55aFwGjYS7PqsD6A-q+Yp9YZmiM6mB4MUYmfR7ro02poxxCQ@mail.gmail.com>
Date: Mon, 28 Apr 2014 15:25:55 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Davidlohr Bueso <davidlohr@...com>
Cc: Hugh Dickins <hughd@...gle.com>,
"Srivatsa S. Bhat" <srivatsa.bhat@...ux.vnet.ibm.com>,
Linux MM <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Rik van Riel <riel@...hat.com>,
Michel Lespinasse <walken@...gle.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>
Subject: Re: [BUG] kernel BUG at mm/vmacache.c:85!
On Mon, Apr 28, 2014 at 3:14 PM, Davidlohr Bueso <davidlohr@...com> wrote:
>
> I think that returning some stale/bogus vma is causing those segfaults
> in udev. It shouldn't occur in a normal scenario. What puzzles me is
> that it's not always reproducible. This makes me wonder what else is
> going on...
I've replaced the BUG_ON() with a WARN_ON_ONCE(), and made it be
unconditional (so you don't have to trigger the range check).
That might make it show up earlier and easier (and hopefully closer to
the place that causes it). Maybe that makes it easier for Srivatsa to
reproduce this. It doesn't make *my* machine do anything different,
though.
Srivatsa? It's in current -git.
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