From: kernel test robot <lkp@intel.com>
To: Nam Cao <namcao@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Gabriele Monaco <gmonaco@redhat.com>,
john.ogness@linutronix.de, linux-trace-kernel@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Nam Cao <namcao@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
Waiman Long <longman@redhat.com>
Subject: Re: [PATCH 04/10] rv: Add rtapp_block monitor
Date: Thu, 13 Mar 2025 23:15:31 +0800 [thread overview]
Message-ID: <202503132244.Azu340js-lkp@intel.com> (raw)
In-Reply-To: <c8a1658c6da343b6055cbfcd6ee5ddea48335d31.1741708239.git.namcao@linutronix.de>
Hi Nam,
kernel test robot noticed the following build warnings:
[auto build test WARNING on trace/for-next]
[also build test WARNING on tip/x86/core tip/x86/mm linus/master v6.14-rc6 next-20250313]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Nam-Cao/rv-Add-undef-TRACE_INCLUDE_FILE/20250312-011043
base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next
patch link: https://lore.kernel.org/r/c8a1658c6da343b6055cbfcd6ee5ddea48335d31.1741708239.git.namcao%40linutronix.de
patch subject: [PATCH 04/10] rv: Add rtapp_block monitor
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20250313/202503132244.Azu340js-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250313/202503132244.Azu340js-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/202503132244.Azu340js-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:91:53: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
91 | static void handle_rt_mutex_wake_waiter_begin(void *, struct task_struct *task)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:96:51: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
96 | static void handle_rt_mutex_wake_waiter_end(void *, struct task_struct *task)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:101:45: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
101 | static void handle_sched_kthread_stop(void *, struct task_struct *task)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:109:49: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
109 | static void handle_sched_kthread_stop_ret(void *, int)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:109:54: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
109 | static void handle_sched_kthread_stop_ret(void *, int)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:117:39: warning: omitting the parameter name in a function definition is a C23 extension [-Wc23-extensions]
117 | static void handle_sched_wakeup(void *, struct task_struct *task)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:164:2: error: call to undeclared function 'check_trace_callback_type_sys_enter'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
164 | rv_attach_trace_probe("rtapp_block", sys_enter, handle_sys_enter);
| ^
include/rv/instrumentation.h:18:3: note: expanded from macro 'rv_attach_trace_probe'
18 | check_trace_callback_type_##tp(rv_handler); \
| ^
<scratch space>:8:1: note: expanded from here
8 | check_trace_callback_type_sys_enter
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:164:2: error: call to undeclared function 'register_trace_sys_enter'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
include/rv/instrumentation.h:19:13: note: expanded from macro 'rv_attach_trace_probe'
19 | WARN_ONCE(register_trace_##tp(rv_handler, NULL), \
| ^
<scratch space>:9:1: note: expanded from here
9 | register_trace_sys_enter
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:165:2: error: call to undeclared function 'check_trace_callback_type_sys_exit'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
165 | rv_attach_trace_probe("rtapp_block", sys_exit, handle_sys_exit);
| ^
include/rv/instrumentation.h:18:3: note: expanded from macro 'rv_attach_trace_probe'
18 | check_trace_callback_type_##tp(rv_handler); \
| ^
<scratch space>:14:1: note: expanded from here
14 | check_trace_callback_type_sys_exit
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:165:2: error: call to undeclared function 'register_trace_sys_exit'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
include/rv/instrumentation.h:19:13: note: expanded from macro 'rv_attach_trace_probe'
19 | WARN_ONCE(register_trace_##tp(rv_handler, NULL), \
| ^
<scratch space>:15:1: note: expanded from here
15 | register_trace_sys_exit
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:165:2: note: did you mean 'register_ftrace_direct'?
include/rv/instrumentation.h:19:13: note: expanded from macro 'rv_attach_trace_probe'
19 | WARN_ONCE(register_trace_##tp(rv_handler, NULL), \
| ^
<scratch space>:15:1: note: expanded from here
15 | register_trace_sys_exit
| ^
include/linux/ftrace.h:535:19: note: 'register_ftrace_direct' declared here
535 | static inline int register_ftrace_direct(struct ftrace_ops *ops, unsigned long addr)
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:180:2: error: call to undeclared function 'unregister_trace_sys_enter'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
180 | rv_detach_trace_probe("rtapp_block", sys_enter, handle_sys_enter);
| ^
include/rv/instrumentation.h:28:3: note: expanded from macro 'rv_detach_trace_probe'
28 | unregister_trace_##tp(rv_handler, NULL); \
| ^
<scratch space>:29:1: note: expanded from here
29 | unregister_trace_sys_enter
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:181:2: error: call to undeclared function 'unregister_trace_sys_exit'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
181 | rv_detach_trace_probe("rtapp_block", sys_exit, handle_sys_exit);
| ^
include/rv/instrumentation.h:28:3: note: expanded from macro 'rv_detach_trace_probe'
28 | unregister_trace_##tp(rv_handler, NULL); \
| ^
<scratch space>:30:1: note: expanded from here
30 | unregister_trace_sys_exit
| ^
kernel/trace/rv/monitors/rtapp_block/rtapp_block.c:181:2: note: did you mean 'unregister_ftrace_direct'?
include/rv/instrumentation.h:28:3: note: expanded from macro 'rv_detach_trace_probe'
28 | unregister_trace_##tp(rv_handler, NULL); \
| ^
<scratch space>:30:1: note: expanded from here
30 | unregister_trace_sys_exit
| ^
include/linux/ftrace.h:539:19: note: 'unregister_ftrace_direct' declared here
539 | static inline int unregister_ftrace_direct(struct ftrace_ops *ops, unsigned long addr,
| ^
6 warnings and 6 errors generated.
vim +91 kernel/trace/rv/monitors/rtapp_block/rtapp_block.c
90
> 91 static void handle_rt_mutex_wake_waiter_begin(void *, struct task_struct *task)
92 {
93 rv_rtapp_block_atom_update(task, RT_MUTEX_WAKING_WAITER, true);
94 }
95
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-03-13 15:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 17:05 [PATCH 00/10] RV: Linear temporal logic monitors for RT application Nam Cao
2025-03-11 17:05 ` Nam Cao
2025-03-11 17:05 ` [PATCH 01/10] rv: Add #undef TRACE_INCLUDE_FILE Nam Cao
2025-03-11 17:05 ` [PATCH 02/10] rv: Let the reactors take care of buffers Nam Cao
2025-03-12 7:58 ` Gabriele Monaco
2025-03-13 8:16 ` Nam Cao
2025-03-13 11:39 ` Gabriele Monaco
2025-03-13 16:07 ` kernel test robot
2025-03-13 16:07 ` kernel test robot
2025-03-11 17:05 ` [PATCH 03/10] rv: Add infrastructure for linear temporal logic monitor Nam Cao
2025-03-12 6:47 ` Gabriele Monaco
2025-03-12 9:56 ` Steven Rostedt
2025-03-12 14:29 ` Nam Cao
2025-03-11 17:05 ` [PATCH 04/10] rv: Add rtapp_block monitor Nam Cao
2025-03-12 7:34 ` Gabriele Monaco
2025-03-13 15:15 ` kernel test robot [this message]
2025-03-11 17:05 ` [PATCH 05/10] x86/tracing: Remove redundant trace_pagefault_key Nam Cao
2025-03-11 17:05 ` [PATCH 06/10] x86/tracing: Move page fault trace points to generic Nam Cao
2025-03-11 17:05 ` [PATCH 07/10] arm64: mm: Add page fault trace points Nam Cao
2025-03-11 17:05 ` [PATCH 08/10] riscv: " Nam Cao
2025-03-11 17:05 ` Nam Cao
2025-04-02 7:35 ` Alexandre Ghiti
2025-04-02 7:35 ` Alexandre Ghiti
2025-03-11 17:05 ` [PATCH 09/10] rv: Add rtapp_pagefault monitor Nam Cao
2025-03-11 17:05 ` Nam Cao
2025-03-11 17:05 ` [PATCH 10/10] rv: raise the number of per-task monitor to 2 Nam Cao
2025-03-12 6:57 ` Gabriele Monaco
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=202503132244.Azu340js-lkp@intel.com \
--to=lkp@intel.com \
--cc=boqun.feng@gmail.com \
--cc=gmonaco@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=namcao@linutronix.de \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=will@kernel.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.