Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-12 Thread Michel Lespinasse
On Fri, Nov 9, 2012 at 6:13 AM, Sasha Levin wrote: > While fuzzing with trinity inside a KVM tools (lkvm) guest, using today's > -next > kernel, I'm getting these: > > [ 117.007714] free gap 7fba0dd1c000, correct 7fba0dcfb000 > [ 117.019773] map_count 750 rb -1 > [ 117.028362] [

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-12 Thread Michel Lespinasse
On Fri, Nov 9, 2012 at 6:13 AM, Sasha Levin levinsasha...@gmail.com wrote: While fuzzing with trinity inside a KVM tools (lkvm) guest, using today's -next kernel, I'm getting these: [ 117.007714] free gap 7fba0dd1c000, correct 7fba0dcfb000 [ 117.019773] map_count 750 rb -1 [ 117.028362]

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-09 Thread Hugh Dickins
On Fri, 9 Nov 2012, Sasha Levin wrote: > On 11/05/2012 05:47 PM, Michel Lespinasse wrote: > > When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is > > correctly set for every vma and that mm->highest_vm_end is also correct. > > > > Also add an explicit 'bug' variable to track if

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-09 Thread Sasha Levin
On 11/05/2012 05:47 PM, Michel Lespinasse wrote: > When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is > correctly set for every vma and that mm->highest_vm_end is also correct. > > Also add an explicit 'bug' variable to track if browse_rb() detected any > invalid condition. > >

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-09 Thread Sasha Levin
On 11/05/2012 05:47 PM, Michel Lespinasse wrote: When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is correctly set for every vma and that mm-highest_vm_end is also correct. Also add an explicit 'bug' variable to track if browse_rb() detected any invalid condition.

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-09 Thread Hugh Dickins
On Fri, 9 Nov 2012, Sasha Levin wrote: On 11/05/2012 05:47 PM, Michel Lespinasse wrote: When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is correctly set for every vma and that mm-highest_vm_end is also correct. Also add an explicit 'bug' variable to track if browse_rb()

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-06 Thread Andrew Morton
On Mon, 5 Nov 2012 14:47:00 -0800 Michel Lespinasse wrote: > When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is > correctly set for every vma and that mm->highest_vm_end is also correct. > > Also add an explicit 'bug' variable to track if browse_rb() detected any > invalid

Re: [PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-06 Thread Andrew Morton
On Mon, 5 Nov 2012 14:47:00 -0800 Michel Lespinasse wal...@google.com wrote: When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is correctly set for every vma and that mm-highest_vm_end is also correct. Also add an explicit 'bug' variable to track if browse_rb() detected any

[PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-05 Thread Michel Lespinasse
When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is correctly set for every vma and that mm->highest_vm_end is also correct. Also add an explicit 'bug' variable to track if browse_rb() detected any invalid condition. Signed-off-by: Michel Lespinasse Reviewed-by: Rik van Riel ---

[PATCH 03/16] mm: check rb_subtree_gap correctness

2012-11-05 Thread Michel Lespinasse
When CONFIG_DEBUG_VM_RB is enabled, check that rb_subtree_gap is correctly set for every vma and that mm-highest_vm_end is also correct. Also add an explicit 'bug' variable to track if browse_rb() detected any invalid condition. Signed-off-by: Michel Lespinasse wal...@google.com Reviewed-by: Rik