From: syzbot ci <syzbot+cif177115980bd6f63@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: Fix ftrace for livepatch + BPF fexit programs
Date: Fri, 24 Oct 2025 01:13:49 -0700 [thread overview]
Message-ID: <68fb353d.a70a0220.3bf6c6.015c.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] Fix ftrace for livepatch + BPF fexit programs
https://lore.kernel.org/all/20251024071257.3956031-1-song@kernel.org
* [PATCH bpf-next 1/3] ftrace: Fix BPF fexit with livepatch
* [PATCH bpf-next 2/3] ftrace: bpf: Fix IPMODIFY + DIRECT in modify_ftrace_direct()
* [PATCH bpf-next 3/3] selftests/bpf: Add tests for livepatch + bpf trampoline
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/05031eb1-929e-442e-8c25-a441c742d58b
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 7361c864852f07b39f5e571447060bd4d758a998
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/0a3a116e-dcd5-4171-83c2-810b34608a0a/config
kernel/bpf/trampoline.c:229:11: error: incomplete definition of type 'struct ftrace_ops'
kernel/bpf/trampoline.c:230:11: error: incomplete definition of type 'struct ftrace_ops'
***
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:
[andrey.grodzovsky@crowdstrike.com andrii@kernel.org ast@kernel.org bpf@vger.kernel.org daniel@iogearbox.net kernel-team@meta.com linux-trace-kernel@vger.kernel.org live-patching@vger.kernel.org mhiramat@kernel.org rostedt@goodmis.org song@kernel.org stable@vger.kernel.org]
If the report looks fine to you, reply with:
#syz upstream
next reply other threads:[~2025-10-24 8:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 8:13 syzbot ci [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-24 20:15 [moderation/CI] Re: Fix ftrace for livepatch + BPF fexit programs 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=68fb353d.a70a0220.3bf6c6.015c.GAE@google.com \
--to=syzbot+cif177115980bd6f63@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