[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<174536763175.2096010.2128821424847053296.git-patchwork-notify@kernel.org>
Date: Wed, 23 Apr 2025 00:20:31 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Feng Yang <yangfeng59949@....com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
martin.lau@...ux.dev, eddyz87@...il.com, song@...nel.org,
yonghong.song@...ux.dev, john.fastabend@...il.com, kpsingh@...nel.org,
sdf@...ichev.me, haoluo@...gle.com, jolsa@...nel.org, hengqi.chen@...il.com,
olsajiri@...il.com, bpf@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v5 bpf-next 0/3] libbpf: Fix event name too long error and add
tests
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Thu, 17 Apr 2025 09:48:45 +0800 you wrote:
> From: Feng Yang <yangfeng@...inos.cn>
>
> Hi everyone,
>
> This series tries to fix event name too long error and add tests.
>
> When the binary path is excessively long, the generated probe_name in libbpf
> exceeds the kernel's MAX_EVENT_NAME_LEN limit (64 bytes).
> This causes legacy uprobe event attachment to fail with error code -22.
>
> [...]
Here is the summary with links:
- [v5,bpf-next,1/3] libbpf: Fix event name too long error
https://git.kernel.org/bpf/bpf-next/c/4dde20b1aa85
- [v5,bpf-next,2/3] selftests/bpf: Add test for attaching uprobe with long event names
https://git.kernel.org/bpf/bpf-next/c/e1be7c45d244
- [v5,bpf-next,3/3] selftests/bpf: Add test for attaching kprobe with long event names
https://git.kernel.org/bpf/bpf-next/c/9b72f3e5b760
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists