From: Pavel Begunkov <asml.silence@gmail.com>
To: Jens Axboe <axboe@kernel.dk>, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing v3 1/1] tests: test io_uring bpf ops
Date: Wed, 18 Mar 2026 20:57:15 +0000 [thread overview]
Message-ID: <c3443f66-5de5-4004-9de4-06ef9d1aa146@gmail.com> (raw)
In-Reply-To: <3c00370f-81b0-41d1-8deb-beb1781a75bd@kernel.dk>
On 3/18/26 18:24, Jens Axboe wrote:
> On 3/18/26 11:43 AM, Pavel Begunkov wrote:
>> On 3/18/26 17:36, Pavel Begunkov wrote:
...
> axboe@m2max ~/gi/liburing (master)> make 6.490s
> make[1]: Entering directory '/home/axboe/git/liburing/src'
> make[1]: Nothing to be done for 'all'.
> make[1]: Leaving directory '/home/axboe/git/liburing/src'
> make[1]: Entering directory '/home/axboe/git/liburing/test'
> mkdir -p output/bpf
> CC output/bpf/nops.bpf.o
> In file included from bpf-progs/nops.bpf.c:3:
> /usr/include/bpf/bpf_helpers.h:318:12: error: conflicting types
I assume it's an outdated libbpf causing issues. I'll kill
vmlinux.h, should be easier this way.
> for 'bpf_stream_vprintk'
> 318 | extern int bpf_stream_vprintk(int stream_id, const char *fmt__str, const void *args,
> | ^
> output/bpf/vmlinux.h:170697:12: note: previous declaration is
> here
> 170697 | extern int bpf_stream_vprintk(int stream_id, const char *fmt__str, const void ...
> | ^
> 1 error generated.
> make[1]: *** [Makefile:379: output/bpf/nops.bpf.o] Error 1
> make[1]: Leaving directory '/home/axboe/git/liburing/test'
> make: *** [Makefile:11: all] Error 2
>
>
--
Pavel Begunkov
next prev parent reply other threads:[~2026-03-18 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 17:36 [PATCH liburing v3 1/1] tests: test io_uring bpf ops Pavel Begunkov
2026-03-18 17:43 ` Pavel Begunkov
2026-03-18 18:24 ` Jens Axboe
2026-03-18 18:28 ` Jens Axboe
2026-03-18 20:57 ` Pavel Begunkov [this message]
2026-03-18 20:59 ` Pavel Begunkov
2026-03-18 21:01 ` Pavel Begunkov
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=c3443f66-5de5-4004-9de4-06ef9d1aa146@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.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