netdev - Re: [PATCH bpf-next] selftests/bpf: Fix parsing of prog types in UAPI hdr for bpftool sync

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]

Date:   Mon, 04 Apr 2022 21:50:12 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Quentin Monnet <quentin@...valent.com>
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org, milan@...verde.com
Subject: Re: [PATCH bpf-next] selftests/bpf: Fix parsing of prog types in UAPI hdr
 for bpftool sync

Hello:

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

On Mon,  4 Apr 2022 15:09:44 +0100 you wrote:
> The script for checking that various lists of types in bpftool remain in
> sync with the UAPI BPF header uses a regex to parse enum bpf_prog_type.
> If this enum contains a set of values different from the list of program
> types in bpftool, it complains.
> 
> This script should have reported the addition, some time ago, of the new
> BPF_PROG_TYPE_SYSCALL, which was not reported to bpftool's program types
> list. It failed to do so, because it failed to parse that new type from
> the enum. This is because the new value, in the BPF header, has an
> explicative comment on the same line, and the regex does not support
> that.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Fix parsing of prog types in UAPI hdr for bpftool sync
    https://git.kernel.org/bpf/bpf-next/c/4eeebce6ac4a

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