From: Catalin Marinas <catalin.marinas@arm.com>
To: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Wei Yongjun <weiyongjun1@huawei.com>,
Chen Jun <chenjun102@huawei.com>,
Aleksandr Mikhalitsyn <aleksandr.mikhalitsyn@canonical.com>,
kernel@openvz.org
Subject: Re: [PATCH 2/2] kmemleak-test: add percpu leak
Date: Tue, 30 Jul 2024 15:17:40 +0100 [thread overview]
Message-ID: <Zqj2BBgAIDb623tZ@arm.com> (raw)
In-Reply-To: <20240725041223.872472-3-ptikhomirov@virtuozzo.com>
On Thu, Jul 25, 2024 at 12:12:16PM +0800, Pavel Tikhomirov wrote:
> Add a per-CPU memory leak, which will be reported like:
>
> unreferenced object 0x3efa840195f8 (size 64):
> comm "modprobe", pid 4667, jiffies 4294688677
> hex dump (first 32 bytes on cpu 0):
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc 0):
> [<ffffffffa7fa87af>] pcpu_alloc+0x3df/0x840
> [<ffffffffc11642d9>] kmemleak_test_init+0x2c9/0x2f0 [kmemleak_test]
> [<ffffffffa7c02264>] do_one_initcall+0x44/0x300
> [<ffffffffa7de9e10>] do_init_module+0x60/0x240
> [<ffffffffa7deb946>] init_module_from_file+0x86/0xc0
> [<ffffffffa7deba99>] idempotent_init_module+0x109/0x2a0
> [<ffffffffa7debd2a>] __x64_sys_finit_module+0x5a/0xb0
> [<ffffffffa88f4f3a>] do_syscall_64+0x7a/0x160
> [<ffffffffa8a0012b>] entry_SYSCALL_64_after_hwframe+0x76/0x7e
>
> CC: Wei Yongjun <weiyongjun1@huawei.com>
> CC: Chen Jun <chenjun102@huawei.com>
> Signed-off-by: Pavel Tikhomirov <ptikhomirov@virtuozzo.com>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
prev parent reply other threads:[~2024-07-30 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 4:12 [PATCH 0/2] kmemleak: support for percpu memory leak detect Pavel Tikhomirov
2024-07-25 4:12 ` [PATCH 1/2] kmemleak: enable tracking for percpu pointers Pavel Tikhomirov
2024-07-30 14:15 ` Catalin Marinas
2024-07-31 2:30 ` Pavel Tikhomirov
2024-07-25 4:12 ` [PATCH 2/2] kmemleak-test: add percpu leak Pavel Tikhomirov
2024-07-30 14:17 ` Catalin Marinas [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=Zqj2BBgAIDb623tZ@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=aleksandr.mikhalitsyn@canonical.com \
--cc=chenjun102@huawei.com \
--cc=kernel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ptikhomirov@virtuozzo.com \
--cc=weiyongjun1@huawei.com \
/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