Re: [PATCH bpf-next v4 00/15] libbpf: type suffixes and autocreate flag for struct_ops maps

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:

On Wed,  6 Mar 2024 12:45:14 +0200 you wrote:
> Tweak struct_ops related APIs to allow the following features:
> - specify version suffixes for stuct_ops map types;
> - share same BPF program between several map definitions with
>   different local BTF types, assuming only maps with same
>   kernel BTF type would be selected for load;
> - toggle autocreate flag for struct_ops maps;
> - automatically toggle autoload for struct_ops programs referenced
>   from struct_ops maps, depending on autocreate status of the
>   corresponding map;
> - use SEC("?.struct_ops") and SEC("?.struct_ops.link")
>   to define struct_ops maps with autocreate == false after object open.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v4,01/15] libbpf: allow version suffixes (___smth) for struct_ops types
    https://git.kernel.org/bpf/bpf-next/c/88972acee1f9
  - [bpf-next,v4,02/15] libbpf: tie struct_ops programs to kernel BTF ids, not to local ids
    https://git.kernel.org/bpf/bpf-next/c/1fcdcca90bf2
  - [bpf-next,v4,03/15] libbpf: honor autocreate flag for struct_ops maps
    https://git.kernel.org/bpf/bpf-next/c/08c5dde48dd0
  - [bpf-next,v4,04/15] selftests/bpf: test struct_ops map definition with type suffix
    https://git.kernel.org/bpf/bpf-next/c/901a9c536f26
  - [bpf-next,v4,05/15] selftests/bpf: utility functions to capture libbpf log in test_progs
    https://git.kernel.org/bpf/bpf-next/c/4597f853d5bc
  - [bpf-next,v4,06/15] selftests/bpf: bad_struct_ops test
    https://git.kernel.org/bpf/bpf-next/c/9c82929ce1bc
  - [bpf-next,v4,07/15] selftests/bpf: test autocreate behavior for struct_ops maps
    https://git.kernel.org/bpf/bpf-next/c/08dfc1369554
  - [bpf-next,v4,08/15] libbpf: sync progs autoload with maps autocreate for struct_ops maps
    https://git.kernel.org/bpf/bpf-next/c/607a50ff2802
  - [bpf-next,v4,09/15] selftests/bpf: verify struct_ops autoload/autocreate sync
    https://git.kernel.org/bpf/bpf-next/c/404855a8c3be
  - [bpf-next,v4,10/15] libbpf: replace elf_state->st_ops_* fields with SEC_ST_OPS sec_type
    https://git.kernel.org/bpf/bpf-next/c/24d9fe302af5
  - [bpf-next,v4,11/15] libbpf: struct_ops in SEC("?.struct_ops") / SEC("?.struct_ops.link")
    https://git.kernel.org/bpf/bpf-next/c/cea716b7850b
  - [bpf-next,v4,12/15] libbpf: rewrite btf datasec names starting from '?'
    https://git.kernel.org/bpf/bpf-next/c/43525abbdb0d
  - [bpf-next,v4,13/15] selftests/bpf: test case for SEC("?.struct_ops")
    https://git.kernel.org/bpf/bpf-next/c/df32d591bf63
  - [bpf-next,v4,14/15] bpf: allow all printable characters in BTF DATASEC names
    https://git.kernel.org/bpf/bpf-next/c/503012aad7f3
  - [bpf-next,v4,15/15] selftests/bpf: test cases for '?' in BTF names
    https://git.kernel.org/bpf/bpf-next/c/bc22f9a13840

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html