From: Quentin Monnet <qmo@kernel.org>
To: Calvin Owens <calvin@wbinvd.org>, Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org
Subject: Re: Need update to libbpf/bpftool for bpf_stream_vprintk() removal (kernel sha 0cecd492f516)
Date: Mon, 9 Mar 2026 20:34:03 +0000 [thread overview]
Message-ID: <e1918475-8028-45a6-a669-dc9031f73c2f@kernel.org> (raw)
In-Reply-To: <aa8KBN1kQnng3yma@mozart.vkv.me>
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.
> I'm happy to send patches if I can help, but I'm guessing this is one of
> those things that is easier to just do yourself with commit access...
>
> Cheers,
> Calvin
>
> [2] https://github.com/libbpf/libbpf/commit/6ddc03d4fe0535ac0fb6c8525db31ac88a018ddd
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0cecd492f516
I take care of bpftool, my ideal workflow is to sync after libbpf has
been updated. Andrii, if you have a moment to do a libbpf sync, I'm
happy to follow up with bpftool.
Quentin
next prev parent reply other threads:[~2026-03-09 20:34 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 [this message]
2026-03-09 23:01 ` Calvin Owens
2026-03-13 3:29 ` Quentin Monnet
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=e1918475-8028-45a6-a669-dc9031f73c2f@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