From: patchwork-bot+netdevbpf@kernel.org
To: Yonghong Song <yonghong.song@linux.dev>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kernel-team@fb.com, martin.lau@kernel.org,
thevlad@meta.com
Subject: Re: [PATCH bpf-next] bpf: Fix kmemleak warnings for percpu hashmap
Date: Mon, 24 Feb 2025 20:20:31 +0000 [thread overview]
Message-ID: <174042843126.3595767.15074738833210480318.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250224175514.2207227-1-yonghong.song@linux.dev>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Mon, 24 Feb 2025 09:55:14 -0800 you wrote:
> Vlad Poenaru from Meta reported the following kmemleak issues:
>
> ...
> unreferenced object 0x606fd7c44ac8 (size 32):
> comm "floodgate_agent", pid 5077, jiffies 4294746072
> hex dump (first 32 bytes on cpu 32):
> 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):
> pcpu_alloc_noprof+0x730/0xeb0
> bpf_map_alloc_percpu+0x69/0xc0
> prealloc_init+0x9d/0x1b0
> htab_map_alloc+0x363/0x510
> map_create+0x215/0x3a0
> __sys_bpf+0x16b/0x3e0
> __x64_sys_bpf+0x18/0x20
> do_syscall_64+0x7b/0x150
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
> unreferenced object 0x606fd7c44ae8 (size 32):
> comm "floodgate_agent", pid 5077, jiffies 4294746072
> hex dump (first 32 bytes on cpu 32):
> d3 08 00 00 00 00 00 00 d3 08 00 00 00 00 00 00 ................
> 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
> backtrace (crc d197b0fe):
> pcpu_alloc_noprof+0x730/0xeb0
> bpf_map_alloc_percpu+0x69/0xc0
> prealloc_init+0x9d/0x1b0
> htab_map_alloc+0x363/0x510
> map_create+0x215/0x3a0
> __sys_bpf+0x16b/0x3e0
> __x64_sys_bpf+0x18/0x20
> do_syscall_64+0x7b/0x150
> entry_SYSCALL_64_after_hwframe+0x4b/0x53
> ...
>
> [...]
Here is the summary with links:
- [bpf-next] bpf: Fix kmemleak warnings for percpu hashmap
https://git.kernel.org/bpf/bpf-next/c/11ba7ce076e5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-02-24 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 17:55 [PATCH bpf-next] bpf: Fix kmemleak warnings for percpu hashmap Yonghong Song
2025-02-24 19:47 ` Martin KaFai Lau
2025-02-24 20:20 ` patchwork-bot+netdevbpf [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=174042843126.3595767.15074738833210480318.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@kernel.org \
--cc=thevlad@meta.com \
--cc=yonghong.song@linux.dev \
/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