Re: [PATCH v2 1/2] tracing: Have eprobes have their own config option
From: Masami Hiramatsu (Google) <mhiramat@kernel.org>
Date: 2025-07-30 10:11:07
Also in:
linux-doc, linux-mm, lkml, oe-kbuild-all
Subsystem:
the rest, tracing · Maintainers:
Linus Torvalds, Steven Rostedt, Masami Hiramatsu
On Wed, 30 Jul 2025 14:27:08 +0800 kernel test robot [off-list ref] wrote:
Hi Steven, kernel test robot noticed the following build errors: [auto build test ERROR on trace/for-next] [also build test ERROR on lwn/docs-next akpm-mm/mm-everything linus/master v6.16 next-20250729] [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/Steven-Rostedt/tracing-Have-eprobes-have-their-own-config-option/20250730-001958 base: https://git.kernel.org/pub/scm/linux/kernel/git/trace/linux-trace for-next patch link: https://lore.kernel.org/r/20250729161912.056641407%40kernel.org patch subject: [PATCH v2 1/2] tracing: Have eprobes have their own config option config: xtensa-randconfig-002-20250730 (https://download.01.org/0day-ci/archive/20250730/202507301452.JPAcMvT0-lkp@intel.com/config) compiler: xtensa-linux-gcc (GCC) 12.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250730/202507301452.JPAcMvT0-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 [off-list ref] | Closes: https://lore.kernel.org/oe-kbuild-all/202507301452.JPAcMvT0-lkp@intel.com/ (local) All errors (new ones prefixed by >>): kernel/trace/trace_probe.c: In function 'parse_probe_arg':quoted
quoted
kernel/trace/trace_probe.c:1105:23: error: implicit declaration of function 'regs_query_register_offset'; did you mean 'ftrace_regs_query_register_offset'? [-Werror=implicit-function-declaration]1105 | ret = regs_query_register_offset(arg + 1); | ^~~~~~~~~~~~~~~~~~~~~~~~~~ | ftrace_regs_query_register_offset cc1: some warnings being treated as errors
Interesting, this find another issue. Since this is provided by CONFIG_PROBE_EVENTS, we need to fix CONFIG_PROBE_EVENTS depending on HAVE_REGS_AND_STACK_ACCESS_API.
diff --git a/kernel/trace/Kconfig b/kernel/trace/Kconfig
index a3f35c7d83b6..cd239240b0ef 100644
--- a/kernel/trace/Kconfig
+++ b/kernel/trace/Kconfig@@ -792,6 +792,7 @@ config DYNAMIC_EVENTS def_bool n config PROBE_EVENTS + depends on HAVE_REGS_AND_STACK_ACCESS_API def_bool n config BPF_KPROBE_OVERRIDE
--
Masami Hiramatsu (Google) <mhiramat@kernel.org>