From: David Ahern <dsahern@kernel.org>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, David Ahern <dsahern@kernel.org>
Subject: [PATCH iproute2-next 0/3] bpf: Work around libbpf deprecations
Date: Sun, 27 Feb 2022 18:58:37 -0700 [thread overview]
Message-ID: <20220228015840.1413-1-dsahern@kernel.org> (raw)
libbpf is deprecating APIs, so iproute2 needs to adapt. This will be
an on-going effort, especially to handle legacy maps. This is a
starter set for the low handing fruit.
David Ahern (3):
bpf_glue: Remove use of bpf_load_program from libbpf
bpf: Export bpf syscall wrapper
bpf: Remove use of bpf_create_map_xattr
include/bpf_util.h | 2 ++
lib/bpf_glue.c | 15 ++++++++-------
lib/bpf_legacy.c | 19 +++++++------------
lib/bpf_libbpf.c | 24 ++++++++++++------------
4 files changed, 29 insertions(+), 31 deletions(-)
--
2.24.3 (Apple Git-128)
next reply other threads:[~2022-02-28 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 1:58 David Ahern [this message]
2022-02-28 1:58 ` [PATCH iproute2-next 1/3] bpf_glue: Remove use of bpf_load_program from libbpf David Ahern
2022-02-28 1:58 ` [PATCH iproute2-next 2/3] bpf: Export bpf syscall wrapper David Ahern
2022-02-28 1:58 ` [PATCH iproute2-next 3/3] bpf: Remove use of bpf_create_map_xattr David Ahern
2022-03-07 16:10 ` [PATCH iproute2-next 0/3] bpf: Work around libbpf deprecations patchwork-bot+netdevbpf
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=20220228015840.1413-1-dsahern@kernel.org \
--to=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).