From: Michael Ellerman <mpe@ellerman.id.au>
To: Denis Kirjanov <kda@linux-powerpc.org>, linuxppc-dev@lists.ozlabs.org
Cc: Denis Kirjanov <kda@linux-powerpc.org>,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [v3] powerpc: msi: mark bitmap with kmemleak_not_leak()
Date: Mon, 12 Oct 2015 22:21:22 +1100 (AEDT) [thread overview]
Message-ID: <20151012112123.3028A140D8F@ozlabs.org> (raw)
In-Reply-To: <1442431574-4575-1-git-send-email-kda@linux-powerpc.org>
On Wed, 2015-16-09 at 19:26:14 UTC, Denis Kirjanov wrote:
> During the MSI bitmap test on boot kmemleak spews the following trace:
>
> unreferenced object 0xc00000016e86c900 (size 64):
> comm "swapper/0", pid 1, jiffies 4294893173 (age 518.024s)
> hex dump (first 32 bytes):
> 00 00 01 ff 7f ff 7f 37 00 00 00 00 00 00 00 00
> .......7........
> ff ff ff ff ff ff ff ff 01 ff ff ff ff
> ff ff ff
> ................
> backtrace:
> [<c00000000003eebc>] .zalloc_maybe_bootmem+0x3c/0x380
> [<c000000000042d6c>] .msi_bitmap_alloc+0x3c/0xb0
> [<c000000000a9aff8>] .msi_bitmap_selftest+0x30/0x2b4
> [<c0000000000090f4>] .do_one_initcall+0xd4/0x270
> [<c000000000a8e250>] .kernel_init_freeable+0x1a0/0x280
> [<c000000000009b5c>] .kernel_init+0x1c/0x120
> [<c000000000007fbc>] .ret_from_kernel_thread+0x58/0x9c
>
> Added a flag to msi_bitmap for tracking allocations
> from slab and memblock so we can properly free/handle
> memory in msi_bitmap_free().
>
> Signed-off-by: Denis Kirjanov <kda@linux-powerpc.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/cb2d3883c6033831e2a93b39
cheers
prev parent reply other threads:[~2015-10-12 11:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-16 19:26 [PATCH v3] powerpc: msi: mark bitmap with kmemleak_not_leak() Denis Kirjanov
2015-09-17 9:25 ` Catalin Marinas
2015-10-02 8:50 ` Denis Kirjanov
2015-10-12 11:21 ` Michael Ellerman [this message]
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=20151012112123.3028A140D8F@ozlabs.org \
--to=mpe@ellerman.id.au \
--cc=catalin.marinas@arm.com \
--cc=kda@linux-powerpc.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).