From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
martin.lau@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH bpf-next 0/7] libbpf: further struct_ops fixes and improvements
Date: Wed, 08 May 2024 00:30:31 +0000 [thread overview]
Message-ID: <171512823186.17947.11978986618832814926.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240507001335.1445325-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:
On Mon, 6 May 2024 17:13:28 -0700 you wrote:
> Fix yet another case of mishandling SEC("struct_ops") programs that were
> nulled out programmatically through BPF skeleton by the user.
>
> While at it, add some improvements around detecting and reporting errors,
> specifically a common case of declaring SEC("struct_ops") program, but
> forgetting to actually make use of it by setting it as a callback
> implementation in SEC(".struct_ops") variable (i.e., map) declaration.
>
> [...]
Here is the summary with links:
- [bpf-next,1/7] libbpf: remove unnecessary struct_ops prog validity check
https://git.kernel.org/bpf/bpf-next/c/8374b56b1df5
- [bpf-next,2/7] libbpf: handle yet another corner case of nulling out struct_ops program
https://git.kernel.org/bpf/bpf-next/c/e18e2e70dbd1
- [bpf-next,3/7] selftests/bpf: add another struct_ops callback use case test
https://git.kernel.org/bpf/bpf-next/c/9d66d60e968d
- [bpf-next,4/7] libbpf: fix libbpf_strerror_r() handling unknown errors
https://git.kernel.org/bpf/bpf-next/c/548c2ede0dc8
- [bpf-next,5/7] libbpf: improve early detection of doomed-to-fail BPF program loading
https://git.kernel.org/bpf/bpf-next/c/c78420bafe7c
- [bpf-next,6/7] selftests/bpf: validate struct_ops early failure detection logic
https://git.kernel.org/bpf/bpf-next/c/41df0733ea41
- [bpf-next,7/7] selftests/bpf: shorten subtest names for struct_ops_module test
https://git.kernel.org/bpf/bpf-next/c/7b9959b8cdbc
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-05-08 0:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-07 0:13 [PATCH bpf-next 0/7] libbpf: further struct_ops fixes and improvements Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 1/7] libbpf: remove unnecessary struct_ops prog validity check Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 2/7] libbpf: handle yet another corner case of nulling out struct_ops program Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 3/7] selftests/bpf: add another struct_ops callback use case test Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 4/7] libbpf: fix libbpf_strerror_r() handling unknown errors Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 5/7] libbpf: improve early detection of doomed-to-fail BPF program loading Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 6/7] selftests/bpf: validate struct_ops early failure detection logic Andrii Nakryiko
2024-05-07 0:13 ` [PATCH bpf-next 7/7] selftests/bpf: shorten subtest names for struct_ops_module test Andrii Nakryiko
2024-05-08 0:30 ` 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=171512823186.17947.11978986618832814926.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=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).