From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, rongtao@cestc.cn,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
song@kernel.org, yonghong.song@linux.dev,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@fomichev.me,
haoluo@google.com, jolsa@kernel.org, bpf@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH bpf-next] samples/bpf: tracex4: Fix failed to create kretprobe 'kmem_cache_alloc_node+0x0'
Date: Tue, 27 Aug 2024 23:20:28 +0000 [thread overview]
Message-ID: <172480082826.787068.693535971609017102.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_34E5BCCAC5ABF3E81222AD81B1D05F16DE06@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 27 Aug 2024 12:30:30 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.cn>
>
> commit 7bd230a26648 ("mm/slab: enable slab allocation tagging for kmalloc
> and friends") [1] swap kmem_cache_alloc_node() to
> kmem_cache_alloc_node_noprof().
>
> linux/samples/bpf$ sudo ./tracex4
> libbpf: prog 'bpf_prog2': failed to create kretprobe
> 'kmem_cache_alloc_node+0x0' perf event: No such file or directory
> ERROR: bpf_program__attach failed
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: tracex4: Fix failed to create kretprobe 'kmem_cache_alloc_node+0x0'
https://git.kernel.org/bpf/bpf-next/c/d205d4af3a5e
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:[~2024-08-27 23:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 4:30 [PATCH bpf-next] samples/bpf: tracex4: Fix failed to create kretprobe 'kmem_cache_alloc_node+0x0' Rong Tao
2024-08-27 23: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=172480082826.787068.693535971609017102.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=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=rongtao@cestc.cn \
--cc=rtoax@foxmail.com \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--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