[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161028142657.3f4b23114737462043a4e109@linux-foundation.org>
Date: Fri, 28 Oct 2016 14:26:57 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Chris Wilson <chris@...is-wilson.co.uk>
Cc: Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org,
sparclinux@...r.kernel.org, linux-mm@...ck.org,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level
page walkers'
On Fri, 28 Oct 2016 21:15:48 +0100 Chris Wilson <chris@...is-wilson.co.uk> wrote:
> > Bisect points to commit 0c79e3331f08 ("mm/vmalloc: replace opencoded 4-level
> > page walkers"). Reverting this patch fixes the problem.
>
> Hmm, apply_to_pte_range() has a BUG_ON(pmd_huge(*pmd)) but the old
> vmap_pte_range() does not and neither has the code to handle that case.
> Presuming that the BUG_ON() there is actually meaningful.
Thanks, I'll drop mm-vmalloc-replace-opencoded-4-level-page-walkers.patch for now.
Powered by blists - more mailing lists