netdev - Re: [PATCH bpf-next 1/2] libbpf: Do not use btf_dump_

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <48c1e6bf-ee4b-bf49-ec85-2cec98ab9dcb@fb.com>
Date:   Thu, 23 Dec 2021 08:13:01 -0800
From:   Yonghong Song <yhs@...com>
To:     Jiri Olsa <jolsa@...hat.com>, Alexei Starovoitov <ast@...nel.org>,
        Daniel Borkmann <daniel@...earbox.net>,
        Andrii Nakryiko <andrii@...nel.org>
CC:     <netdev@...r.kernel.org>, <bpf@...r.kernel.org>,
        Martin KaFai Lau <kafai@...com>,
        Song Liu <songliubraving@...com>,
        John Fastabend <john.fastabend@...il.com>,
        KP Singh <kpsingh@...omium.org>
Subject: Re: [PATCH bpf-next 1/2] libbpf: Do not use btf_dump__new macro for
 c++ objects



On 12/23/21 5:17 AM, Jiri Olsa wrote:
> As reported in here [0], C++ compilers don't support __builtin_types_compatible_p(),
> so at least don't screw up compilation for them and let C++ users
> pick btf_dump__new vs btf_dump__new_deprecated explicitly.
> 
> [0] https://github.com/libbpf/libbpf/issues/283#issuecomment-986100727
> Fixes: 6084f5dc928f ("libbpf: Ensure btf_dump__new() and btf_dump_opts are future-proof")
> Signed-off-by: Andrii Nakryiko <andrii@...nel.org>
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>

Acked-by: Yonghong Song <yhs@...com>