Archive-only list for syzbot
 help / color / mirror / Atom feed
From: syzbot ci <syzbot+ci39ad38d3bb2c360c@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: bpf trampoline support "jmp" mode
Date: Fri, 14 Nov 2025 02:32:32 -0800	[thread overview]
Message-ID: <69170540.a70a0220.3124cb.004b.GAE@google.com> (raw)

syzbot ci has tested the following series

[v1] bpf trampoline support "jmp" mode
https://lore.kernel.org/all/20251114092450.172024-1-dongml2@chinatelecom.cn
* [PATCH RFC bpf-next 1/7] ftrace: introduce FTRACE_OPS_FL_JMP
* [PATCH RFC bpf-next 2/7] x86/ftrace: implement DYNAMIC_FTRACE_WITH_JMP
* [PATCH RFC bpf-next 3/7] bpf: fix the usage of BPF_TRAMP_F_SKIP_FRAME
* [PATCH RFC bpf-next 4/7] bpf,x86: adjust the "jmp" mode for bpf trampoline
* [PATCH RFC bpf-next 5/7] bpf: introduce bpf_arch_text_poke_type
* [PATCH RFC bpf-next 6/7] bpf,x86: implement bpf_arch_text_poke_type for x86_64
* [PATCH RFC bpf-next 7/7] bpf: implement "jmp" mode for trampoline

and found the following issue:
kernel build error

Full report is available here:
https://ci.syzbot.org/series/94b38701-bd30-4339-be30-e395e6237f5b

***

kernel build error

tree:      bpf-next
URL:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base:      026bcf9c286c42aacc34359a18aebcc1787f12d2
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/c564f88b-ade0-465f-87ea-bb953779c1de/config

kernel/bpf/trampoline.c:499:11: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:499:22: error: use of undeclared identifier 'FTRACE_OPS_FL_JMP'
kernel/bpf/trampoline.c:501:11: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:501:23: 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 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


             reply	other threads:[~2025-11-14 10:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 10:32 syzbot ci [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-17  4:36 [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=69170540.a70a0220.3124cb.004b.GAE@google.com \
    --to=syzbot+ci39ad38d3bb2c360c@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