lkml.org 
[lkml]   [2014]   [Sep]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: kmemleak: Cannot insert [...] into the object search tree (overlaps existing) (mm: use memblock_alloc_range())
From
2014-09-03 2:10 GMT+09:00 Sabrina Dubroca <sd@queasysnail.net>:
> Hello,
>
> 2014-08-24, 23:56:03 +0900, Akinobu Mita wrote:
>> Replace memblock_find_in_range() and memblock_reserve() with
>> memblock_alloc_range().
>>
>> Signed-off-by: Akinobu Mita <akinobu.mita@gmail.com>
>> Cc: linux-mm@kvack.org
>
> This patch is included in linux-next, and when I boot next-20140901,
> on a 32-bit build, I get this message:
>
>
> kmemleak: Cannot insert 0xf6556000 into the object search tree (overlaps existing)

kmemleak_alloc() in memblock_virt_alloc_internal() should have been removed by
the conversion in this patch. Otherwise kmemleak() is called twice because
memblock_alloc_range() also calls it.

Andrew, could you drop this patch for now. I'll send the patch with this fix.

Thanks for the report.


\
 
 \ /
  Last update: 2014-09-03 01:41    [W:0.045 / U:1.284 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site