From: Quentin Monnet <qmo@kernel.org>
To: Calvin Owens <calvin@wbinvd.org>
Cc: Andrii Nakryiko <andrii@kernel.org>, bpf@vger.kernel.org
Subject: Re: Need update to libbpf/bpftool for bpf_stream_vprintk() removal (kernel sha 0cecd492f516)
Date: Fri, 13 Mar 2026 03:29:45 +0000 [thread overview]
Message-ID: <a8f6460d-bd36-4563-a731-80eb31ea72fc@kernel.org> (raw)
In-Reply-To: <aa9RLM_OwFmI8X8l@mozart.vkv.me>
2026-03-09 16:01 UTC-0700 ~ Calvin Owens <calvin@wbinvd.org>
> On Monday 03/09 at 20:34 +0000, Quentin Monnet wrote:
>> 2026-03-09 10:57 UTC-0700 ~ Calvin Owens <calvin@wbinvd.org>
>>> Hi Andrii,
>>>
>>> Your libbpf github sync at [1] happened just before [2] was merged...
>>> would you mind syncing that bpf_helpers.h change into libbpf/bpftool?
>>>
>>> In file included from skeleton/profiler.bpf.c:4:
>>> libbpf/include/bpf/bpf_helpers.h:318:12: error: conflicting types for 'bpf_stream_vprintk'
>>> 318 | extern int bpf_stream_vprintk(int stream_id, const char *fmt__str, const void *args,
>>> | ^
>>> ./vmlinux.h:128001:12: note: previous declaration is here
>>> 128001 | extern int bpf_stream_vprintk(int stream_id, const char *fmt__str, const void *args, u32 len__sz) __weak __ksym;
>>
>>
>> Hi, where did you observe that, please? I don't see it when compiling
>> bpftool from the main branch of the GitHub repo.
>
> Hi Quentin,
>
> Thanks for looking, apologies for not adding you to the initial mail.
>
> It's bpftool-7.6.0 with libbpf-1.6.2 that is failing to build in my
> case (with 7.0-rc kernels), exactly what is described here:
>
> https://github.com/libbpf/libbpf/issues/947
Ok, reading your first message I thought the error was when compiling
bpftool itself. Now I get it, thanks.
> I think it was just "bad luck" that it missed Andrii's sync, it was
> committed in the kernel 18 hours after his sync. But maybe I'm assuming
> too much from the timing...
Ihor and Andrii synced the libbpf mirror a few hours ago, and I just
updated the bpftool repo, so you should be able to pull the fix from there.
Best regards,
Quentin
prev parent reply other threads:[~2026-03-13 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 17:57 Need update to libbpf/bpftool for bpf_stream_vprintk() removal (kernel sha 0cecd492f516) Calvin Owens
2026-03-09 20:34 ` Quentin Monnet
2026-03-09 23:01 ` Calvin Owens
2026-03-13 3:29 ` Quentin Monnet [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=a8f6460d-bd36-4563-a731-80eb31ea72fc@kernel.org \
--to=qmo@kernel.org \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=calvin@wbinvd.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