From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>
Subject: lib/sys_info.c:154:17: error: implicit declaration of function 'ftrace_dump'; did you mean 'ftrace_bug'?
Date: Sun, 16 Aug 2026 15:27:48 +0200 [thread overview]
Message-ID: <202608161520.80bt1KHN-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Steven-Rostedt/tracing-Move-non-trace_printk-prototypes-back-to-kernel-h/20260814-235157
head: 5803c3be0223106fdafb05968cefd241bf88fef1
commit: 5803c3be0223106fdafb05968cefd241bf88fef1 tracing: Add CONFIG_TRACE_PRINTK_DEBUGGING to clean up kernel.h
date: 2 days ago
config: x86_64-rhel-9.4-bpf (https://download.01.org/0day-ci/archive/20260816/202608161520.80bt1KHN-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260816/202608161520.80bt1KHN-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202608161520.80bt1KHN-lkp@intel.com/
All errors (new ones prefixed by >>):
lib/sys_info.c: In function '__sys_info':
>> lib/sys_info.c:154:17: error: implicit declaration of function 'ftrace_dump'; did you mean 'ftrace_bug'? [-Wimplicit-function-declaration]
154 | ftrace_dump(DUMP_ALL);
| ^~~~~~~~~~~
| ftrace_bug
>> lib/sys_info.c:154:29: error: 'DUMP_ALL' undeclared (first use in this function)
154 | ftrace_dump(DUMP_ALL);
| ^~~~~~~~
lib/sys_info.c:154:29: note: each undeclared identifier is reported only once for each function it appears in
--
samples/trace_printk/trace-printk.c: In function 'trace_printk_irq_work':
>> samples/trace_printk/trace-printk.c:20:9: error: implicit declaration of function 'trace_printk'; did you mean 'early_printk'? [-Wimplicit-function-declaration]
20 | trace_printk("(irq) This is a static string that will use trace_bputs\n");
| ^~~~~~~~~~~~
| early_printk
--
drivers/tty/sysrq.c: In function 'sysrq_ftrace_dump':
>> drivers/tty/sysrq.c:331:9: error: implicit declaration of function 'ftrace_dump'; did you mean 'ftrace_bug'? [-Wimplicit-function-declaration]
331 | ftrace_dump(DUMP_ALL);
| ^~~~~~~~~~~
| ftrace_bug
>> drivers/tty/sysrq.c:331:21: error: 'DUMP_ALL' undeclared (first use in this function)
331 | ftrace_dump(DUMP_ALL);
| ^~~~~~~~
drivers/tty/sysrq.c:331:21: note: each undeclared identifier is reported only once for each function it appears in
--
In file included from kernel/rcu/tree.c:70:
kernel/rcu/tree_stall.h: In function 'rcu_stall_kick_kthreads':
kernel/rcu/rcu.h:337:17: error: implicit declaration of function 'ftrace_dump'; did you mean 'ftrace_bug'? [-Wimplicit-function-declaration]
337 | ftrace_dump(oops_dump_mode); \
| ^~~~~~~~~~~
kernel/rcu/tree_stall.h:238:17: note: in expansion of macro 'rcu_ftrace_dump'
238 | rcu_ftrace_dump(DUMP_ALL);
| ^~~~~~~~~~~~~~~
>> kernel/rcu/tree_stall.h:238:33: error: 'DUMP_ALL' undeclared (first use in this function)
238 | rcu_ftrace_dump(DUMP_ALL);
| ^~~~~~~~
kernel/rcu/rcu.h:337:29: note: in definition of macro 'rcu_ftrace_dump'
337 | ftrace_dump(oops_dump_mode); \
| ^~~~~~~~~~~~~~
kernel/rcu/tree_stall.h:238:33: note: each undeclared identifier is reported only once for each function it appears in
238 | rcu_ftrace_dump(DUMP_ALL);
| ^~~~~~~~
kernel/rcu/rcu.h:337:29: note: in definition of macro 'rcu_ftrace_dump'
337 | ftrace_dump(oops_dump_mode); \
| ^~~~~~~~~~~~~~
kernel/rcu/tree_stall.h: In function 'check_cpu_stall':
kernel/rcu/tree_stall.h:859:41: error: 'DUMP_ALL' undeclared (first use in this function)
859 | rcu_ftrace_dump(DUMP_ALL);
| ^~~~~~~~
kernel/rcu/rcu.h:337:29: note: in definition of macro 'rcu_ftrace_dump'
337 | ftrace_dump(oops_dump_mode); \
| ^~~~~~~~~~~~~~
vim +154 lib/sys_info.c
d747755917bf8a Feng Tang 2025-07-03 138
03ef32d665e8a2 Feng Tang 2025-11-13 139 static void __sys_info(unsigned long si_mask)
b76e89e50fc369 Feng Tang 2025-07-03 140 {
b76e89e50fc369 Feng Tang 2025-07-03 141 if (si_mask & SYS_INFO_TASKS)
b76e89e50fc369 Feng Tang 2025-07-03 142 show_state();
b76e89e50fc369 Feng Tang 2025-07-03 143
b76e89e50fc369 Feng Tang 2025-07-03 144 if (si_mask & SYS_INFO_MEM)
b76e89e50fc369 Feng Tang 2025-07-03 145 show_mem();
b76e89e50fc369 Feng Tang 2025-07-03 146
b76e89e50fc369 Feng Tang 2025-07-03 147 if (si_mask & SYS_INFO_TIMERS)
b76e89e50fc369 Feng Tang 2025-07-03 148 sysrq_timer_list_show();
b76e89e50fc369 Feng Tang 2025-07-03 149
b76e89e50fc369 Feng Tang 2025-07-03 150 if (si_mask & SYS_INFO_LOCKS)
b76e89e50fc369 Feng Tang 2025-07-03 151 debug_show_all_locks();
b76e89e50fc369 Feng Tang 2025-07-03 152
b76e89e50fc369 Feng Tang 2025-07-03 153 if (si_mask & SYS_INFO_FTRACE)
b76e89e50fc369 Feng Tang 2025-07-03 @154 ftrace_dump(DUMP_ALL);
b76e89e50fc369 Feng Tang 2025-07-03 155
760fc597c33d5a Andy Shevchenko 2025-10-30 156 if (si_mask & SYS_INFO_ALL_BT)
b76e89e50fc369 Feng Tang 2025-07-03 157 trigger_all_cpu_backtrace();
b76e89e50fc369 Feng Tang 2025-07-03 158
b76e89e50fc369 Feng Tang 2025-07-03 159 if (si_mask & SYS_INFO_BLOCKED_TASKS)
b76e89e50fc369 Feng Tang 2025-07-03 160 show_state_filter(TASK_UNINTERRUPTIBLE);
b76e89e50fc369 Feng Tang 2025-07-03 161 }
03ef32d665e8a2 Feng Tang 2025-11-13 162
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-16 13:28 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=202608161520.80bt1KHN-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.