From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Borkmann Subject: Re: [PATCH bpf-next 0/5] Introduce libbpf_attach_type_by_name Date: Thu, 27 Sep 2018 21:21:59 +0200 Message-ID: <9bc18e3a-dfb7-d2cc-7d7e-5aa860fb3074@iogearbox.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: ast@kernel.org, kernel-team@fb.com To: Andrey Ignatov , netdev@vger.kernel.org Return-path: Received: from www62.your-server.de ([213.133.104.62]:49941 "EHLO www62.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728213AbeI1Blt (ORCPT ); Thu, 27 Sep 2018 21:41:49 -0400 In-Reply-To: Content-Language: en-US Sender: netdev-owner@vger.kernel.org List-ID: On 09/27/2018 12:24 AM, Andrey Ignatov wrote: > This patch set introduces libbpf_attach_type_by_name function in libbpf to > identify attach type by section name. > > This is useful to avoid writing same logic over and over again in user > space applications that leverage libbpf. > > Patch 1 has more details on the new function and problem being solved. > Patches 2 and 3 add support for new section names. > Patch 4 uses new function in a selftest. > Patch 5 adds selftest for libbpf_{prog,attach}_type_by_name. > > As a side note there are a lot of inconsistencies now between names used by > libbpf and bpftool (e.g. cgroup/skb vs cgroup_skb, cgroup_device and device > vs cgroup/dev, sockops vs sock_ops, etc). This patch set does not address > it but it tries not to make it harder to address it in the future. > > > Andrey Ignatov (5): > libbpf: Introduce libbpf_attach_type_by_name > libbpf: Support cgroup_skb/{e,in}gress section names > libbpf: Support sk_skb/stream_{parser,verdict} section names > selftests/bpf: Use libbpf_attach_type_by_name in test_socket_cookie > selftests/bpf: Test libbpf_{prog,attach}_type_by_name Applied to bpf-next, thanks Andrey!