netdev - Re: [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware

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: 
 <169265822645.19025.15250374334018816513.git-patchwork-notify@kernel.org>
Date: Mon, 21 Aug 2023 22:50:26 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Daniel T. Lee <danieltimlee@...il.com>
Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
 martin.lau@...ux.dev, song@...nel.org, yonghong.song@...ux.dev,
 john.fastabend@...il.com, kpsingh@...nel.org, sdf@...gle.com,
 haoluo@...gle.com, jolsa@...nel.org, axboe@...nel.dk,
 johannes.thumshirn@....com, netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: [bpf-next 0/9] samples/bpf: make BPF programs more libbpf aware

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:

On Fri, 18 Aug 2023 18:01:10 +0900 you wrote:
> The existing tracing programs have been developed for a considerable
> period of time and, as a result, do not properly incorporate the
> features of the current libbpf, such as CO-RE. This is evident in
> frequent usage of functions like PT_REGS* and the persistence of "hack"
> methods using underscore-style bpf_probe_read_kernel from the past.
> These programs are far behind the current level of libbpf and can
> potentially confuse users.
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/9] samples/bpf: fix warning with ignored-attributes
    https://git.kernel.org/bpf/bpf-next/c/34f6e38f58db
  - [bpf-next,2/9] samples/bpf: convert to vmlinux.h with tracing programs
    https://git.kernel.org/bpf/bpf-next/c/e7e6c774f5d4
  - [bpf-next,3/9] samples/bpf: unify bpf program suffix to .bpf with tracing programs
    https://git.kernel.org/bpf/bpf-next/c/4a0ee7889069
  - [bpf-next,4/9] samples/bpf: fix symbol mismatch by compiler optimization
    https://git.kernel.org/bpf/bpf-next/c/02dabc247ad6
  - [bpf-next,5/9] samples/bpf: make tracing programs to be more CO-RE centric
    https://git.kernel.org/bpf/bpf-next/c/11430421b440
  - [bpf-next,6/9] samples/bpf: fix bio latency check with tracepoint
    https://git.kernel.org/bpf/bpf-next/c/92632115fb57
  - [bpf-next,7/9] samples/bpf: fix broken map lookup probe
    https://git.kernel.org/bpf/bpf-next/c/d93a7cf6ca2c
  - [bpf-next,8/9] samples/bpf: refactor syscall tracing programs using BPF_KSYSCALL macro
    https://git.kernel.org/bpf/bpf-next/c/8dc805514631
  - [bpf-next,9/9] samples/bpf: simplify spintest with kprobe.multi
    https://git.kernel.org/bpf/bpf-next/c/456d53554ca7

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