From: syzbot ci <syzbot+ci776c8b6bec447c54@syzkaller.appspotmail.com>
To: syzkaller-upstream-moderation@googlegroups.com
Cc: syzbot@lists.linux.dev
Subject: [moderation/CI] Re: ftrace,bpf: Use single direct ops for bpf trampolines
Date: Tue, 23 Sep 2025 15:45:23 -0700 [thread overview]
Message-ID: <68d32303.a70a0220.4f78.0010.GAE@google.com> (raw)
syzbot ci has tested the following series
[v1] ftrace,bpf: Use single direct ops for bpf trampolines
https://lore.kernel.org/all/20250923215147.1571952-1-jolsa@kernel.org
* [PATCH 1/9] ftrace: Make alloc_and_copy_ftrace_hash direct friendly
* [PATCH 2/9] ftrace: Add register_ftrace_direct_hash function
* [PATCH 3/9] ftrace: Add unregister_ftrace_direct_hash function
* [PATCH 4/9] ftrace: Add modify_ftrace_direct_hash function
* [PATCH 5/9] ftrace: Export some of hash related functions
* [PATCH 6/9] ftrace: Use direct hash interface in direct functions
* [PATCH 7/9] bpf: Add trampoline ip hash table
* [PATCH 8/9] ftrace: Factor ftrace_ops ops_func interface
* [PATCH 9/9] bpf, x86: Use single ftrace_ops for direct calls
and found the following issue:
kernel build error
Full report is available here:
https://ci.syzbot.org/series/d43b97e0-0a8d-4035-8052-301be44fb4ba
***
kernel build error
tree: bpf-next
URL: https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next.git
base: 5a427fddec5e76360725a0f03df3a2a003efbe2e
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/22bf6a56-bac1-4606-9b59-4fe45ae685dd/config
kernel/trace/trace.h:907:24: error: incomplete definition of type 'struct ftrace_hash'
kernel/trace/trace.h:907:40: error: incomplete definition of type 'struct ftrace_hash'
***
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 jolsa@kernel.org linux-arm-kernel@lists.infradead.org linux-kernel@vger.kernel.org linux-trace-kernel@vger.kernel.org mark.rutland@arm.com menglong8.dong@gmail.com revest@google.com rostedt@kernel.org]
If the report looks fine to you, reply with:
#syz upstream
reply other threads:[~2025-09-23 22:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68d32303.a70a0220.4f78.0010.GAE@google.com \
--to=syzbot+ci776c8b6bec447c54@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