[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <166787041460.14648.14053712268169387053.git-patchwork-notify@kernel.org>
Date: Tue, 08 Nov 2022 01:20:14 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Rong Tao <rtoax@...mail.com>
Cc: andrii.nakryiko@...il.com, andrii@...nel.org, ast@...nel.org,
bpf@...r.kernel.org, daniel@...earbox.net, haoluo@...gle.com,
john.fastabend@...il.com, jolsa@...nel.org, kpsingh@...nel.org,
linux-kernel@...r.kernel.org, martin.lau@...ux.dev,
rongtao@...tc.cn, sdf@...gle.com, song@...nel.org, yhs@...com
Subject: Re: [PATCH bpf-next] samples/bpf: Fix sockex3 error: missing BPF prog
type
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:
On Sat, 5 Nov 2022 14:48:00 +0800 you wrote:
> From: Rong Tao <rongtao@...tc.cn>
>
> since commit 450b167fb9be("libbpf: clean up SEC() handling"),
> sec_def_matches() does not recognize "socket/xxx" as "socket", therefore,
> the BPF program type is not recognized.
>
> Instead of sockex3_user.c parsing section names to get the BPF program fd.
> We use the program array map to assign a static index to each BPF program
> (get inspired by selftests/bpf progs/test_prog_array_init.c).
> Therefore, use SEC("socket") as section name instead of SEC("socket/xxx"),
> so that the BPF program is parsed to SOCKET_FILTER type. The "missing BPF
> prog type" problem is solved.
>
> [...]
Here is the summary with links:
- [bpf-next] samples/bpf: Fix sockex3 error: missing BPF prog type
https://git.kernel.org/bpf/bpf-next/c/e5659e4e19e4
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