From: Stephen Hemminger <stephen@networkplumber.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: netdev@vger.kernel.org, dsahern@kernel.org,
Thomas Graf <tgraf@suug.ch>,
Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@plumgrid.com>,
Jiri Pirko <jiri@resnulli.us>
Subject: Re: [PATCH iproute2-next 3/5] tc: remove eBPF map export and exec bpf import
Date: Thu, 19 Nov 2026 09:47:11 -0800 [thread overview]
Message-ID: <20261119094711.6049b21a@phoenix.local> (raw)
In-Reply-To: <CAM0EoMkLUeJdzCBxsknqxSKAZ2Q7WhAB9ifV_tKXne4fPxY7YA@mail.gmail.com>
On Thu, 19 Nov 2026 04:19:50 -0500
Jamal Hadi Salim <jhs@mojatatu.com> wrote:
> I dont think this code changes in iproute2-next (didnt try iproute2
> tree) - but for tc testing i use:
> https://git.kernel.org/pub/scm/network/iproute2/iproute2-next.git
> (origin/main = 9eee7bb8 ("Merge remote-tracking branch 'main/main'
> into next", 2026-11-18))
> libbpf 1.3.0 default and LIBBPF_FORCE=off
>
> m_bpf.c:107:25: error: 'bpf_obj' undeclared (first use in this function)
> m_bpf.c:108:25: error: 'bpf_uds_name' undeclared (first use in
> this function)
> m_bpf.c:108:43: error: 'struct bpf_cfg_in' has no member named 'uds'
> make[1]: *** [../config.mk:47: m_bpf.o] Error 1
> make: *** [Makefile:67: all] Error 2
>
> suspect: the patch removes this declaration?
> - const char *bpf_obj = NULL, *bpf_uds_name = NULL;
>
> Attached fixes it.
I suspect you need to do a "make distclean" and rebuild.
There should no longer be and --libbpf options in config and no way to force off.
next prev parent reply other threads:[~2026-11-19 17:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 0:15 [PATCH iproute2-next 0/5] bpf: fix mount point parsing and drop the legacy loader Stephen Hemminger
2026-11-19 0:15 ` [PATCH iproute2-next 1/5] lib/bpf: parse /proc/mounts with getmntent and check fs magic Stephen Hemminger
2026-11-19 0:15 ` [PATCH iproute2-next 2/5] lib/fs: " Stephen Hemminger
2026-11-19 0:15 ` [PATCH iproute2-next 3/5] tc: remove eBPF map export and exec bpf import Stephen Hemminger
2026-11-19 9:19 ` Jamal Hadi Salim
2026-11-19 9:50 ` Jamal Hadi Salim
2026-11-19 17:35 ` Stephen Hemminger
2026-11-19 17:47 ` Stephen Hemminger [this message]
2026-11-19 20:12 ` Jamal Hadi Salim
2026-11-19 0:15 ` [PATCH iproute2-next 4/5] lib/bpf: require libbpf and remove legacy ELF loader Stephen Hemminger
2026-11-19 0:15 ` [PATCH iproute2-next 5/5] lib/bpf: check for missing bpf fs mount point Stephen Hemminger
2026-11-19 10:16 ` Toke Høiland-Jørgensen
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=20261119094711.6049b21a@phoenix.local \
--to=stephen@networkplumber.org \
--cc=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=dsahern@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.