From: patchwork-bot+netdevbpf@kernel.org
To: Wang Yufen <wangyufen@huawei.com>
Cc: bpf@vger.kernel.org, netdev@vger.kernel.org, ast@kernel.org,
daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, yhs@fb.com,
joe@wand.net.nz
Subject: Re: [PATCH bpf v4] bpf: Fix memory leaks in __check_func_call
Date: Tue, 08 Nov 2022 18:50:15 +0000 [thread overview]
Message-ID: <166793341502.24064.11585625251989325212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1667884291-15666-1-git-send-email-wangyufen@huawei.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Tue, 8 Nov 2022 13:11:31 +0800 you wrote:
> kmemleak reports this issue:
>
> unreferenced object 0xffff88817139d000 (size 2048):
> comm "test_progs", pid 33246, jiffies 4307381979 (age 45851.820s)
> hex dump (first 32 bytes):
> 01 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:
> [<0000000045f075f0>] kmalloc_trace+0x27/0xa0
> [<0000000098b7c90a>] __check_func_call+0x316/0x1230
> [<00000000b4c3c403>] check_helper_call+0x172e/0x4700
> [<00000000aa3875b7>] do_check+0x21d8/0x45e0
> [<000000001147357b>] do_check_common+0x767/0xaf0
> [<00000000b5a595b4>] bpf_check+0x43e3/0x5bc0
> [<0000000011e391b1>] bpf_prog_load+0xf26/0x1940
> [<0000000007f765c0>] __sys_bpf+0xd2c/0x3650
> [<00000000839815d6>] __x64_sys_bpf+0x75/0xc0
> [<00000000946ee250>] do_syscall_64+0x3b/0x90
> [<0000000000506b7f>] entry_SYSCALL_64_after_hwframe+0x63/0xcd
>
> [...]
Here is the summary with links:
- [bpf,v4] bpf: Fix memory leaks in __check_func_call
https://git.kernel.org/bpf/bpf/c/eb86559a691c
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:[~2022-11-08 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 5:11 [PATCH bpf v4] bpf: Fix memory leaks in __check_func_call Wang Yufen
2022-11-08 18:50 ` 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=166793341502.24064.11585625251989325212.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=joe@wand.net.nz \
--cc=john.fastabend@gmail.com \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=wangyufen@huawei.com \
--cc=yhs@fb.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