From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/3] package/libbpf: update UAPI header installation work-around
Date: Fri, 4 Sep 2026 14:17:41 +0200 [thread overview]
Message-ID: <20260904121741.404200-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260827095520.1049186-1-thomas.petazzoni@bootlin.com>
In reply of:
> bpftrace often needs very recent kernel headers, more recent than the
> runtime version actually needed. We already had a workaround in
> libbpf making sure that if the kernel headers are older than 6.1, we
> would install the libbpf provided headers instead.
>
> As we are about to update bpftrace to a newer version that uses
> BPF_TRACE_KPROBE_SESSION, which was introduced in Linux 6.10, we need
> to update this workaround accordingly and ensure that the libbpf
> header is installed if the kernel headers are older than 6.10.
>
> This is necessary for the update of bpftrace to 0.26.1.
>
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Applied to 2026.05.x. Thanks
> ---
> package/libbpf/libbpf.mk | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/package/libbpf/libbpf.mk b/package/libbpf/libbpf.mk
> index 5a6d574331..0683ec12c1 100644
> --- a/package/libbpf/libbpf.mk
> +++ b/package/libbpf/libbpf.mk
> @@ -18,14 +18,12 @@ define LIBBPF_BUILD_CMDS
> -C $(@D)/src
> endef
>
> -# bpftrace uses bpf_iter_link_info.task that was added since kernel 6.1
> +# bpftrace uses BPF_TRACE_KPROBE_SESSION that was added since kernel 6.10
> # so we need to update some uapi headers in STAGING_DIR if the toolchain
> -# is build with linux-headers < 6.1.
> +# is build with linux-headers < 6.1.0
> # Otherwise bpftrace is broken due to out of date linux/bpf.h installed
> # by the toolchain.
> -# https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=f0d74c4da1f060d2a66976193712a5e6abd361f5
> -# https://github.com/bpftrace/bpftrace/commit/7578314df67df6bbdffaf493ff3b4d182b235b34
> -ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_1),)
> +ifeq ($(BR2_TOOLCHAIN_HEADERS_AT_LEAST_6_10),)
> LIBBPF_UPDATE_UAPI_HEADERS = install_uapi_headers UAPIDIR=/usr/include/bpf
>
> define LIBBPF_FIX_STAGING_PC
> --
> 2.55.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2026-09-04 12:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 9:55 [Buildroot] [PATCH 1/3] package/libbpf: update UAPI header installation work-around Thomas Petazzoni via buildroot
2026-08-27 9:55 ` [Buildroot] [PATCH 2/3] package/bpftrace: bump to version 0.26.1 to fix build with LLVM 22 Thomas Petazzoni via buildroot
2026-09-04 12:17 ` Thomas Perale via buildroot
2026-08-27 9:55 ` [Buildroot] [PATCH 3/3] support/testing: add bpftrace test Thomas Petazzoni via buildroot
2026-08-29 14:19 ` Peter Korsgaard
2026-08-29 16:52 ` Julien Olivain via buildroot
2026-08-29 17:49 ` Peter Korsgaard
2026-08-29 18:45 ` Thomas Petazzoni via buildroot
2026-08-29 19:24 ` Julien Olivain via buildroot
2026-09-04 12:19 ` Thomas Perale via buildroot
2026-08-28 10:58 ` [Buildroot] [PATCH 1/3] package/libbpf: update UAPI header installation work-around Julien Olivain via buildroot
2026-09-04 12:17 ` Thomas Perale via buildroot [this message]
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=20260904121741.404200-1-thomas.perale@mind.be \
--to=buildroot@buildroot.org \
--cc=thomas.perale@mind.be \
--cc=thomas.petazzoni@bootlin.com \
/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