From: syzbot ci <syzbot+ci13fbaa7d5915781a@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bpf trampoline support "jmp" mode
Date: Sun, 16 Nov 2025 20:36:51 -0800 [thread overview]
Message-ID: <691aa663.a70a0220.3124cb.008f.GAE@google.com> (raw)
syzbot ci has tested the following series
[v2] bpf trampoline support "jmp" mode
https://lore.kernel.org/all/20251117034906.32036-1-dongml2@chinatelecom.cn
* [PATCH bpf-next v2 1/6] ftrace: introduce FTRACE_OPS_FL_JMP
* [PATCH bpf-next v2 2/6] x86/ftrace: implement DYNAMIC_FTRACE_WITH_JMP
* [PATCH bpf-next v2 3/6] bpf: fix the usage of BPF_TRAMP_F_SKIP_FRAME
* [PATCH bpf-next v2 4/6] bpf,x86: adjust the "jmp" mode for bpf trampoline
* [PATCH bpf-next v2 5/6] bpf: specify the old and new poke_type for bpf_arch_text_poke
* [PATCH bpf-next v2 6/6] bpf: implement "jmp" mode for trampoline
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/b597c752-a7b9-40fa-9a32-641b73182e64
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 4722981cca373a338bbcf3a93ecf7144a892b03b
arch: amd64
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
config: https://ci.syzbot.org/builds/53f87e2d-9838-46d8-afda-0347a66e697a/config
kernel/bpf/trampoline.c:500:11: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:500:22: error: use of undeclared identifier 'FTRACE_OPS_FL_JMP'
kernel/bpf/trampoline.c:502:11: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:502:23: error: use of undeclared identifier 'FTRACE_OPS_FL_JMP'
kernel/bpf/trampoline.c:534:12: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:534:23: error: use of undeclared identifier 'FTRACE_OPS_FL_JMP'
kernel/bpf/trampoline.c:536:12: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:536:24: error: use of undeclared identifier 'FTRACE_OPS_FL_JMP'
***
If these findings have caused you to resend the series or submit a
separate fix, please add the following tag to your commit message:
Tested-by: syzbot@syzkaller.appspotmail.com
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
The email will later be sent to:
[andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net eddyz87@gmail.com haoluo@google.com jiang.biao@linux.dev john.fastabend@gmail.com jolsa@kernel.org kpsingh@kernel.org linux-kernel@vger.kernel.org linux-trace-kernel@vger.kernel.org mark.rutland@arm.com martin.lau@linux.dev mathieu.desnoyers@efficios.com menglong8.dong@gmail.com mhiramat@kernel.org rostedt@goodmis.org sdf@fomichev.me song@kernel.org yonghong.song@linux.dev]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-11-17 4:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 4:36 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-14 10:32 [moderation/CI] Re: bpf trampoline support "jmp" mode syzbot ci
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=691aa663.a70a0220.3124cb.008f.GAE@google.com \
--to=syzbot+ci13fbaa7d5915781a@syzkaller.appspotmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzkaller-upstream-moderation@googlegroups.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