Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrii Nakryiko <andriin@fb.com>
To: <bpf@vger.kernel.org>, <netdev@vger.kernel.org>, <ast@fb.com>,
<daniel@iogearbox.net>
Cc: <andrii.nakryiko@gmail.com>, <kernel-team@fb.com>,
Andrii Nakryiko <andriin@fb.com>
Subject: [PATCH bpf-next 0/4] libbpf: minimize feature detection (reallocarray, libelf-mmap)
Date: Tue, 18 Aug 2020 14:59:04 -0700 [thread overview]
Message-ID: <20200818215908.2746786-1-andriin@fb.com> (raw)
Get rid of two feature detectors: reallocarray and libelf-mmap. Optional
feature detections complicate libbpf Makefile and cause more troubles for
various applications that want to integrate libbpf as part of their build.
Patch #1 replaces all reallocarray() uses into libbpf-internal reallocarray()
implementation. Patches #2 and #3 makes sure we won't re-introduce
reallocarray() accidentally. Patch #2 also removes last use of
libbpf_internal.h header inside bpftool. There is still nlattr.h that's used
by both libbpf and bpftool, but that's left for a follow up patch to split.
Patch #4 removed libelf-mmap feature detector and all its uses, as it's
trivial to handle missing mmap support in libbpf, the way objtool has been
doing it for a while.
Andrii Nakryiko (4):
libbpf: remove any use of reallocarray() in libbpf
tools/bpftool: remove libbpf_internal.h usage in bpftool
libbpf: centralize poisoning and poison reallocarray()
tools: remove feature-libelf-mmap feature detection
tools/bpf/bpftool/gen.c | 2 -
tools/bpf/bpftool/net.c | 299 +++++++++++++++++++++++--
tools/build/Makefile.feature | 1 -
tools/build/feature/Makefile | 4 -
tools/build/feature/test-all.c | 4 -
tools/build/feature/test-libelf-mmap.c | 9 -
tools/lib/bpf/Makefile | 10 +-
tools/lib/bpf/bpf.c | 3 -
tools/lib/bpf/bpf_prog_linfo.c | 3 -
tools/lib/bpf/btf.c | 14 +-
tools/lib/bpf/btf_dump.c | 9 +-
tools/lib/bpf/hashmap.c | 3 +
tools/lib/bpf/libbpf.c | 38 ++--
tools/lib/bpf/libbpf_internal.h | 44 +++-
tools/lib/bpf/libbpf_probes.c | 3 -
tools/lib/bpf/netlink.c | 128 +----------
tools/lib/bpf/nlattr.c | 9 +-
tools/lib/bpf/ringbuf.c | 8 +-
tools/lib/bpf/xsk.c | 3 -
tools/perf/Makefile.config | 4 -
tools/perf/util/symbol.h | 2 +-
21 files changed, 353 insertions(+), 247 deletions(-)
delete mode 100644 tools/build/feature/test-libelf-mmap.c
--
2.24.1
next reply other threads:[~2020-08-18 21:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 21:59 Andrii Nakryiko [this message]
2020-08-18 21:59 ` [PATCH bpf-next 1/4] libbpf: remove any use of reallocarray() in libbpf Andrii Nakryiko
2020-08-18 21:59 ` [PATCH bpf-next 2/4] tools/bpftool: remove libbpf_internal.h usage in bpftool Andrii Nakryiko
2020-08-18 21:59 ` [PATCH bpf-next 3/4] libbpf: centralize poisoning and poison reallocarray() Andrii Nakryiko
2020-08-18 21:59 ` [PATCH bpf-next 4/4] tools: remove feature-libelf-mmap feature detection Andrii Nakryiko
2020-08-19 1:08 ` Alexei Starovoitov
2020-08-19 1:19 ` Andrii Nakryiko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200818215908.2746786-1-andriin@fb.com \
--to=andriin@fb.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@fb.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=netdev@vger.kernel.org \
--subject='Re: [PATCH bpf-next 0/4] libbpf: minimize feature detection (reallocarray, libelf-mmap)' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).