From: patchwork-bot+netdevbpf@kernel.org
To: Rong Tao <rtoax@foxmail.com>
Cc: andrii.nakryiko@gmail.com, andrii@kernel.org, ast@kernel.org,
bpf@vger.kernel.org, daniel@iogearbox.net, haoluo@google.com,
john.fastabend@gmail.com, jolsa@kernel.org, kpsingh@kernel.org,
linux-kernel@vger.kernel.org, martin.lau@linux.dev,
rongtao@cestc.cn, sdf@google.com, song@kernel.org, yhs@fb.com
Subject: Re: [PATCH bpf-next] samples/bpf: Fix sockex3 error: missing BPF prog type
Date: Tue, 08 Nov 2022 01:20:14 +0000 [thread overview]
Message-ID: <166787041460.14648.14053712268169387053.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <tencent_EBA3C18864069E42175946973C2ACBAF5408@qq.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Sat, 5 Nov 2022 14:48:00 +0800 you wrote:
> From: Rong Tao <rongtao@cestc.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
prev parent reply other threads:[~2022-11-08 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 13:33 [PATCH] samples/bpf: Fix sockex3: " Rong Tao
2022-10-27 13:38 ` [PATCH bpf-next] " Rong Tao
2022-10-27 20:15 ` Andrii Nakryiko
2022-10-28 1:01 ` [PATCH] " Rong Tao
2022-10-28 17:09 ` Andrii Nakryiko
2022-10-29 7:53 ` [PATCH bpf-next] " Rong Tao
2022-11-03 18:38 ` Andrii Nakryiko
2022-11-04 3:17 ` Rong Tao
2022-11-04 22:53 ` Andrii Nakryiko
2022-11-05 6:48 ` [PATCH bpf-next] samples/bpf: Fix sockex3 error: " Rong Tao
2022-11-08 1:14 ` Andrii Nakryiko
2022-11-08 1: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=166787041460.14648.14053712268169387053.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--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@google.com \
--cc=song@kernel.org \
--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
all inboxes | Powered by JetHome®