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: Tue, 10 Dec 2019 10:47:06 -0800 From: Andrii Nakryiko <andrii.nakryiko@...il.com> To: Jakub Kicinski <jakub.kicinski@...ronome.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, Dec 10, 2019 at 10:17 AM Jakub Kicinski <jakub.kicinski@...ronome.com> wrote: > > 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. > https://lkml.org/lkml/2019/11/27/1264 > My recollection is that only you and Alexei thought it was > a good/workable idea. Daniel and others didn't seem to mind either.
Powered by blists - more mailing lists