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 PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 19 Jan 2022 04:00:10 +0000 From: patchwork-bot+netdevbpf@...nel.org To: Toke Høiland-Jørgensen <toke@...hat.com>@ci.codeaurora.org Cc: ast@...nel.org, daniel@...earbox.net, andrii@...nel.org, kafai@...com, songliubraving@...com, yhs@...com, john.fastabend@...il.com, kpsingh@...nel.org, netdev@...r.kernel.org, bpf@...r.kernel.org Subject: Re: [PATCH bpf] libbpf: define BTF_KIND_* constants in btf.h to avoid compilation errors Hello: This patch was applied to bpf/bpf-next.git (master) by Andrii Nakryiko <andrii@...nel.org>: On Tue, 18 Jan 2022 15:13:27 +0100 you wrote: > The btf.h header included with libbpf contains inline helper functions to > check for various BTF kinds. These helpers directly reference the > BTF_KIND_* constants defined in the kernel header, and because the header > file is included in user applications, this happens in the user application > compile units. > > This presents a problem if a user application is compiled on a system with > older kernel headers because the constants are not available. To avoid > this, add #defines of the constants directly in btf.h before using them. > > [...] Here is the summary with links: - [bpf] libbpf: define BTF_KIND_* constants in btf.h to avoid compilation errors https://git.kernel.org/bpf/bpf-next/c/eaa266d83a37 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists