netdev - Re: [PATCH bpf-next 03/15] libbpf: move non-public APIs from libbpf.h to libbpf

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

Message-ID: <20191210101716.56c34afc@cakuba.netronome.com>
Date:   Tue, 10 Dec 2019 10:17:16 -0800
From:   Jakub Kicinski <jakub.kicinski@...ronome.com>
To:     Andrii Nakryiko <andrii.nakryiko@...il.com>
Cc:     Andrii Nakryiko <andriin@...com>, bpf <bpf@...r.kernel.org>,
        Networking <netdev@...r.kernel.org>,
        Alexei Starovoitov <ast@...com>,
        Daniel Borkmann <daniel@...earbox.net>,
        Kernel Team <kernel-team@...com>
Subject: Re: [PATCH bpf-next 03/15] libbpf: move non-public APIs from
 libbpf.h to libbpf_internal.h

On Tue, 10 Dec 2019 09:04:58 -0800, Andrii Nakryiko wrote:
> > I thought this idea was unpopular when proposed?  
> 
> There was a recent discussion about the need for unstable APIs to be
> exposed to bpftool and we concluded that libbpf_internal.h is the most
> appropriate place to do this.

Mm. Do you happen to have lore link? Can't find now.

My recollection is that only you and Alexei thought it was
a good/workable idea.