netdev - Re: [PATCH bpf-next v8 0/6] Support associating BPF programs with struct

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <176498275203.1878807.11776031951947151435.git-patchwork-notify@kernel.org>
Date: Sat, 06 Dec 2025 00:59:12 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Amery Hung <ameryhung@...il.com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org, alexei.starovoitov@...il.com,
 andrii@...nel.org, daniel@...earbox.net, tj@...nel.org,
 martin.lau@...nel.org, kernel-team@...a.com
Subject: Re: [PATCH bpf-next v8 0/6] Support associating BPF programs with
 struct_ops

Hello:

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

On Wed,  3 Dec 2025 15:37:42 -0800 you wrote:
> Hi,
> 
> This patchset adds a new BPF command BPF_PROG_ASSOC_STRUCT_OPS to
> the bpf() syscall to allow associating a BPF program with a struct_ops.
> The command is introduced to address a emerging need from struct_ops
> users. As the number of subsystems adopting struct_ops grows, more
> users are building their struct_ops-based solution with some help from
> other BPF programs. For example, scx_layer uses a syscall program as
> a user space trigger to refresh layers [0]. It also uses tracing program
> to infer whether a task is using GPU and needs to be prioritized [1]. In
> these use cases, when there are multiple struct_ops instances, the
> struct_ops kfuncs called from different BPF programs, whether struct_ops
> or not needs to be able to refer to a specific one, which currently is
> not possible.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v8,1/6] bpf: Allow verifier to fixup kernel module kfuncs
    https://git.kernel.org/bpf/bpf-next/c/1588c81b9f21
  - [bpf-next,v8,2/6] bpf: Support associating BPF program with struct_ops
    https://git.kernel.org/bpf/bpf-next/c/b5709f6d26d6
  - [bpf-next,v8,3/6] libbpf: Add support for associating BPF program with struct_ops
    https://git.kernel.org/bpf/bpf-next/c/87cd177b149a
  - [bpf-next,v8,4/6] selftests/bpf: Test BPF_PROG_ASSOC_STRUCT_OPS command
    https://git.kernel.org/bpf/bpf-next/c/33a165f9c2c1
  - [bpf-next,v8,5/6] selftests/bpf: Test ambiguous associated struct_ops
    https://git.kernel.org/bpf/bpf-next/c/04fd12df4e05
  - [bpf-next,v8,6/6] selftests/bpf: Test getting associated struct_ops in timer callback
    https://git.kernel.org/bpf/bpf-next/c/0e841d19263a

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