netdev - Re: [PATCH v2 bpf 1/2] libbpf: Ignore non function pointer member in 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 for Android: free password hash cracker in your pocket

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

Message-Id: <161316000730.8234.4257657674013138235.git-patchwork-notify@kernel.org>
Date:   Fri, 12 Feb 2021 20:00:07 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Martin KaFai Lau <kafai@...com>
Cc:     bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
        kernel-team@...com, netdev@...r.kernel.org, andrii@...nel.org
Subject: Re: [PATCH v2 bpf 1/2] libbpf: Ignore non function pointer member in
 struct_ops

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Thu, 11 Feb 2021 18:10:30 -0800 you wrote:
> When libbpf initializes the kernel's struct_ops in
> "bpf_map__init_kern_struct_ops()", it enforces all
> pointer types must be a function pointer and rejects
> others.  It turns out to be too strict.  For example,
> when directly using "struct tcp_congestion_ops" from vmlinux.h,
> it has a "struct module *owner" member and it is set to NULL
> in a bpf_tcp_cc.o.
> 
> [...]

Here is the summary with links:
  - [v2,bpf,1/2] libbpf: Ignore non function pointer member in struct_ops
    https://git.kernel.org/bpf/bpf-next/c/d2836dddc95d
  - [v2,bpf,2/2] bpf: selftests: Add non function pointer test to struct_ops
    https://git.kernel.org/bpf/bpf-next/c/a79e88dd2ca6

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