linux-kernel - Re: kmemleak: Cannot insert [...] into the object search tree (overlaps existing) (mm: use memblock_alloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAC5umygz-bsrWJErmyaLE25cXCpXHpw5uiKeM7-pD+KvKtjmxw@mail.gmail.com>
Date:	Wed, 3 Sep 2014 08:04:20 +0900
From:	Akinobu Mita <akinobu.mita@...il.com>
To:	Sabrina Dubroca <sd@...asysnail.net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org
Subject: Re: kmemleak: Cannot insert [...] into the object search tree
 (overlaps existing) (mm: use memblock_alloc_range())

2014-09-03 2:10 GMT+09:00 Sabrina Dubroca <sd@...asysnail.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@...il.com>
>> Cc: linux-mm@...ck.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/