From: Steven Rostedt <rostedt@goodmis.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Christian Loehle <Christian.Loehle@arm.com>,
"pr-tracker-bot@kernel.org" <pr-tracker-bot@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Hongyan Xia <Hongyan.Xia2@arm.com>,
LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@kernel.org>,
Mark Rutland <Mark.Rutland@arm.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Andrew Morton <akpm@linux-foundation.org>,
Haiyue Wang <haiyuewa@163.com>,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Sasha Levin <sashal@kernel.org>,
Sven Schnelle <svens@linux.ibm.com>,
Tengda Wu <wutengda@huaweicloud.com>
Subject: Re: [GIT PULL] ftrace: Updates for 6.15
Date: Tue, 1 Apr 2025 10:10:21 -0400 [thread overview]
Message-ID: <20250401101021.2aa9ed2c@gandalf.local.home> (raw)
In-Reply-To: <20250401113159.GA83216@unreal>
On Tue, 1 Apr 2025 14:31:59 +0300
Leon Romanovsky <leon@kernel.org> wrote:
> We see same issue in our CI systems.
>
> 13:29:09 + make -s -j64 ARCH=x86
> 13:32:31 ld: kernel/trace/trace_output.o: in function `print_function_args':
> 13:32:31 /home/jenkins/agent/workspace/kernel_build/linux/kernel/trace/trace_output.c:713:(.text+0x20f1): undefined reference to `btf_find_func_proto'
> 13:32:31 ld: /home/jenkins/agent/workspace/kernel_build/linux/kernel/trace/trace_output.c:717:(.text+0x210d): undefined reference to `btf_get_func_param'
> 13:32:31 make[2]: *** [scripts/Makefile.vmlinux:77: vmlinux] Error 1
> 13:32:31 make[1]: *** [/home/jenkins/agent/workspace/kernel_build/linux/Makefile:1234: vmlinux] Error 2
> 13:32:31 make: *** [Makefile:251: __sub-make] Error 2
Looks like a dependency is missing and/or an #ifdef block needs to be added.
Thanks for the report, I'll take a look into it.
-- Steve
prev parent reply other threads:[~2025-04-01 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 23:39 Steven Rostedt
2025-03-28 0:09 ` pr-tracker-bot
2025-03-31 16:57 ` Christian Loehle
2025-04-01 11:26 ` Christian Loehle
2025-04-01 11:31 ` Leon Romanovsky
2025-04-01 14:10 ` Steven Rostedt [this message]
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=20250401101021.2aa9ed2c@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=Christian.Loehle@arm.com \
--cc=Hongyan.Xia2@arm.com \
--cc=Mark.Rutland@arm.com \
--cc=akpm@linux-foundation.org \
--cc=haiyuewa@163.com \
--cc=jiapeng.chong@linux.alibaba.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=pr-tracker-bot@kernel.org \
--cc=sashal@kernel.org \
--cc=svens@linux.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=wutengda@huaweicloud.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
all inboxes | Powered by JetHome®