From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com
Subject: Re: [PATCH bpf-next 0/4] Preparatory libbpf fixes and clean ups
Date: Wed, 17 Aug 2022 21:00:16 +0000 [thread overview]
Message-ID: <166077001646.24755.9118958959698337211.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220816001929.369487-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 15 Aug 2022 17:19:25 -0700 you wrote:
> Few fixes and clean up in preparation for finalizing libbpf 1.0.
>
> Main change is switching libbpf to initializing only relevant portions of
> union bpf_attr for any given BPF command. This has been on a wishlist for
> a while, so finally this is done. While cleaning this up, I've also cleaned up
> few other placed were we didn't use explicit memset() with kernel UAPI structs
> (perf_event_attr, bpf_map_info, bpf_prog_info, etc).
>
> [...]
Here is the summary with links:
- [bpf-next,1/4] libbpf: fix potential NULL dereference when parsing ELF
https://git.kernel.org/bpf/bpf-next/c/d4e6d684f3be
- [bpf-next,2/4] libbpf: streamline bpf_attr and perf_event_attr initialization
https://git.kernel.org/bpf/bpf-next/c/813847a31447
- [bpf-next,3/4] libbpf: clean up deprecated and legacy aliases
https://git.kernel.org/bpf/bpf-next/c/abf84b64e36b
- [bpf-next,4/4] selftests/bpf: few fixes for selftests/bpf built in release mode
https://git.kernel.org/bpf/bpf-next/c/df78da27260c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-08-17 21:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-16 0:19 [PATCH bpf-next 0/4] Preparatory libbpf fixes and clean ups Andrii Nakryiko
2022-08-16 0:19 ` [PATCH bpf-next 1/4] libbpf: fix potential NULL dereference when parsing ELF Andrii Nakryiko
2022-08-16 21:31 ` Hao Luo
2022-08-16 0:19 ` [PATCH bpf-next 2/4] libbpf: streamline bpf_attr and perf_event_attr initialization Andrii Nakryiko
2022-08-16 21:33 ` Hao Luo
2022-08-16 21:54 ` Andrii Nakryiko
2022-08-16 0:19 ` [PATCH bpf-next 3/4] libbpf: clean up deprecated and legacy aliases Andrii Nakryiko
2022-08-16 21:33 ` Hao Luo
2022-08-16 21:55 ` Andrii Nakryiko
2022-08-16 0:19 ` [PATCH bpf-next 4/4] selftests/bpf: few fixes for selftests/bpf built in release mode Andrii Nakryiko
2022-08-16 21:34 ` Hao Luo
2022-08-16 21:58 ` Andrii Nakryiko
2022-08-17 21:00 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-08-16 0:13 [PATCH bpf-next 0/4] Preparatory libbpf fixes and clean ups Andrii Nakryiko
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=166077001646.24755.9118958959698337211.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@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