Messages in this thread | | | Date | Wed, 3 Sep 2014 08:04:20 +0900 | Subject | Re: kmemleak: Cannot insert [...] into the object search tree (overlaps existing) (mm: use memblock_alloc_range()) | From | Akinobu Mita <> |
| |
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.
| |