Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2017-01-09 Thread David Miller
From: Chris Wilson Date: Mon, 9 Jan 2017 11:37:07 + > Could some mm expert explain why it is safe for mm/vmalloc.c to ignore > huge pud/pmd that raise BUG_ON in the same code in mm/memory.c > (vmap_pmd_range() vs apply_to_pmd_range())? > > At a guess, is sparc64

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2017-01-09 Thread David Miller
From: Chris Wilson Date: Mon, 9 Jan 2017 11:37:07 + > Could some mm expert explain why it is safe for mm/vmalloc.c to ignore > huge pud/pmd that raise BUG_ON in the same code in mm/memory.c > (vmap_pmd_range() vs apply_to_pmd_range())? > > At a guess, is sparc64 covering the init_mm with a

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2017-01-09 Thread Chris Wilson
On Fri, Oct 28, 2016 at 10:18:25AM -0700, Guenter Roeck wrote: > Hi, > > when running sparc64 images in qemu, I see the following crash. > This is with next-20161028. > > [2.530785] clocksource: jiffies: mask: 0x max_cycles: > 0x,max_idle_ns: 1911260446275 ns > [

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2017-01-09 Thread Chris Wilson
On Fri, Oct 28, 2016 at 10:18:25AM -0700, Guenter Roeck wrote: > Hi, > > when running sparc64 images in qemu, I see the following crash. > This is with next-20161028. > > [2.530785] clocksource: jiffies: mask: 0x max_cycles: > 0x,max_idle_ns: 1911260446275 ns > [

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Andrew Morton
On Fri, 28 Oct 2016 21:15:48 +0100 Chris Wilson 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 >

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Andrew Morton
On Fri, 28 Oct 2016 21:15:48 +0100 Chris Wilson 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

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Chris Wilson
On Fri, Oct 28, 2016 at 10:18:25AM -0700, Guenter Roeck wrote: > Hi, > > when running sparc64 images in qemu, I see the following crash. > This is with next-20161028. > > [2.530785] clocksource: jiffies: mask: 0x max_cycles: > 0x,max_idle_ns: 1911260446275 ns > [

Re: Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Chris Wilson
On Fri, Oct 28, 2016 at 10:18:25AM -0700, Guenter Roeck wrote: > Hi, > > when running sparc64 images in qemu, I see the following crash. > This is with next-20161028. > > [2.530785] clocksource: jiffies: mask: 0x max_cycles: > 0x,max_idle_ns: 1911260446275 ns > [

Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Guenter Roeck
Hi, when running sparc64 images in qemu, I see the following crash. This is with next-20161028. [2.530785] clocksource: jiffies: mask: 0x max_cycles: 0x,max_idle_ns: 1911260446275 ns [2.532359] kernel BUG at mm/memory.c:1881! [2.532798] \|/ \|/

Crash in -next due to 'mm/vmalloc: replace opencoded 4-level page walkers'

2016-10-28 Thread Guenter Roeck
Hi, when running sparc64 images in qemu, I see the following crash. This is with next-20161028. [2.530785] clocksource: jiffies: mask: 0x max_cycles: 0x,max_idle_ns: 1911260446275 ns [2.532359] kernel BUG at mm/memory.c:1881! [2.532798] \|/ \|/