Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-16 Thread Andrea Arcangeli
Hi Kirill, On Mon, Apr 14, 2014 at 05:42:18PM +0300, Kirill A. Shutemov wrote: > I've spent few day trying to understand rmap code. And now I think my > patch is wrong. > > I actually don't see where walk order requirement comes from. It seems all > operations (insert, remove, foreach) on anon_vm

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-14 Thread Kirill A. Shutemov
On Thu, Apr 10, 2014 at 06:27:50PM +0200, Andrea Arcangeli wrote: > Hi, > > On Thu, Apr 10, 2014 at 04:44:36PM +0300, Kirill A. Shutemov wrote: > > Okay, below is my attempt to fix the bug. I'm not entirely sure it's > > correct. Andrea, could you take a look? > > The possibility the interval tre

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Andrea Arcangeli
Hi, On Thu, Apr 10, 2014 at 04:44:36PM +0300, Kirill A. Shutemov wrote: > Okay, below is my attempt to fix the bug. I'm not entirely sure it's > correct. Andrea, could you take a look? The possibility the interval tree implicitly broke the walk order of the anon_vma list didn't cross my mind, tha

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Sasha Levin
On 04/10/2014 10:37 AM, Dave Jones wrote: > On Thu, Apr 10, 2014 at 04:45:58PM +0800, Bob Liu wrote: > > On Tue, Apr 8, 2014 at 10:37 PM, Sasha Levin > wrote: > > > Hi all, > > > > > > While fuzzing with trinity inside a KVM tools guest running the latest > -next > > > kernel, I've stumbled

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Dave Jones
On Thu, Apr 10, 2014 at 04:45:58PM +0800, Bob Liu wrote: > On Tue, Apr 8, 2014 at 10:37 PM, Sasha Levin wrote: > > Hi all, > > > > While fuzzing with trinity inside a KVM tools guest running the latest > > -next > > kernel, I've stumbled on the following: > > > > Wow! There are so many

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Kirill A. Shutemov
On Thu, Apr 10, 2014 at 01:25:27PM +0300, Kirill A. Shutemov wrote: > On Tue, Apr 08, 2014 at 10:37:05AM -0400, Sasha Levin wrote: > > Hi all, > > > > While fuzzing with trinity inside a KVM tools guest running the latest -next > > kernel, I've stumbled on the following: > > > > [ 1275.253114] ke

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Kirill A. Shutemov
On Tue, Apr 08, 2014 at 10:37:05AM -0400, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools guest running the latest -next > kernel, I've stumbled on the following: > > [ 1275.253114] kernel BUG at mm/huge_memory.c:1829! > [ 1275.253642] invalid opcode: [#1] PREE

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Kirill A. Shutemov
On Tue, Apr 08, 2014 at 10:37:05AM -0400, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools guest running the latest -next > kernel, I've stumbled on the following: > > [ 1275.253114] kernel BUG at mm/huge_memory.c:1829! > [ 1275.253642] invalid opcode: [#1] PREE

Re: mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-10 Thread Bob Liu
On Tue, Apr 8, 2014 at 10:37 PM, Sasha Levin wrote: > Hi all, > > While fuzzing with trinity inside a KVM tools guest running the latest -next > kernel, I've stumbled on the following: > Wow! There are so many huge memory related bugs recently. AFAIR, there were still several without fix. I wanna

mm: kernel BUG at mm/huge_memory.c:1829!

2014-04-08 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest running the latest -next kernel, I've stumbled on the following: [ 1275.253114] kernel BUG at mm/huge_memory.c:1829! [ 1275.253642] invalid opcode: [#1] PREEMPT SMP DEBUG_PAGEALLOC [ 1275.254775] Dumping ftrace buffer: [ 1275.255631