[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191021125557.GM26267@pc-63.home>
Date: Mon, 21 Oct 2019 14:55:57 +0200
From: Daniel Borkmann <daniel@...earbox.net>
To: Andrii Nakryiko <andriin@...com>
Cc: bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...com,
andrii.nakryiko@...il.com, kernel-team@...com
Subject: Re: [PATCH bpf-next 0/7] Auto-guess program type on bpf_object__open
On Sun, Oct 20, 2019 at 08:38:55PM -0700, Andrii Nakryiko wrote:
> This patch set's main goal is to teach bpf_object__open() (and its variants)
> to automatically derive BPF program type/expected attach type from section
> names, similarly to how bpf_prog_load() was doing it. This significantly
> improves user experience by eliminating yet another
> obvious-only-in-the-hindsight surprise, when using libbpf APIs.
>
> There are a bunch of auxiliary clean-ups and improvements. E.g.,
> bpf_program__get_type() and bpf_program__get_expected_attach_type() are added
> for completeness and symmetry with corresponding setter APIs. Some clean up
> and fixes in selftests/bpf are done as well.
>
> Andrii Nakryiko (7):
> tools: sync if_link.h
> libbpf: add bpf_program__get_{type, expected_attach_type) APIs
> libbpf: add uprobe/uretprobe and tp/raw_tp section suffixes
> libbpf: teach bpf_object__open to guess program types
> selftests/bpf: make a copy of subtest name
> selftests/bpf: make reference_tracking test use subtests
> selftest/bpf: get rid of a bunch of explicit BPF program type setting
Looks good, applied, thanks!
Powered by blists - more mailing lists