From: Akinobu Mita <akinobu.mita@gmail.com>
To: Sabrina Dubroca <sd@queasysnail.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: kmemleak: Cannot insert [...] into the object search tree (overlaps existing) (mm: use memblock_alloc_range())
Date: Wed, 3 Sep 2014 08:04:20 +0900 [thread overview]
Message-ID: <CAC5umygz-bsrWJErmyaLE25cXCpXHpw5uiKeM7-pD+KvKtjmxw@mail.gmail.com> (raw)
In-Reply-To: <20140902171036.GA12406@kria>
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.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-09-02 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-24 14:56 [PATCH 1/2] x86: use memblock_alloc_range() or memblock_alloc_base() Akinobu Mita
2014-08-24 14:56 ` [PATCH 2/2] mm: use memblock_alloc_range() Akinobu Mita
2014-09-02 17:10 ` kmemleak: Cannot insert [...] into the object search tree (overlaps existing) (mm: use memblock_alloc_range()) Sabrina Dubroca
2014-09-02 23:04 ` Akinobu Mita [this message]
2014-08-27 20:53 ` [PATCH 1/2] x86: use memblock_alloc_range() or memblock_alloc_base() Andrew Morton
2014-08-28 15:50 ` Akinobu Mita
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAC5umygz-bsrWJErmyaLE25cXCpXHpw5uiKeM7-pD+KvKtjmxw@mail.gmail.com \
--to=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sd@queasysnail.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox