All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH v3 2/4] ftrace: Add support for function argument to graph tracer
Date: Thu, 27 Feb 2025 22:00:05 +0800	[thread overview]
Message-ID: <202502272155.zS8WsTRz-lkp@intel.com> (raw)
In-Reply-To: <20250225222653.724198940@goodmis.org>

Hi Steven,

kernel test robot noticed the following build errors:

[auto build test ERROR on linus/master]
[also build test ERROR on v6.14-rc4 next-20250227]
[cannot apply to trace/for-next]
[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/ftrace-Add-print_function_args/20250226-063252
base:   linus/master
patch link:    https://lore.kernel.org/r/20250225222653.724198940%40goodmis.org
patch subject: [PATCH v3 2/4] ftrace: Add support for function argument to graph tracer
config: arm-socfpga_defconfig (https://download.01.org/0day-ci/archive/20250227/202502272155.zS8WsTRz-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250227/202502272155.zS8WsTRz-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/202502272155.zS8WsTRz-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from include/linux/ftrace.h:115,
                    from kernel/trace/trace_functions_graph.c:11:
   kernel/trace/trace_functions_graph.c: In function '__graph_entry':
>> include/linux/ftrace_regs.h:22:9: error: implicit declaration of function 'regs_get_kernel_argument'; did you mean 'regs_get_kernel_stack_nth'? [-Wimplicit-function-declaration]
      22 |         regs_get_kernel_argument(&arch_ftrace_regs(fregs)->regs, n)
         |         ^~~~~~~~~~~~~~~~~~~~~~~~
   kernel/trace/trace_functions_graph.c:137:42: note: in expansion of macro 'ftrace_regs_get_argument'
     137 |                         entry->args[i] = ftrace_regs_get_argument(fregs, i);
         |                                          ^~~~~~~~~~~~~~~~~~~~~~~~
   kernel/trace/trace_functions_graph.c: In function 'print_graph_entry_leaf':
   kernel/trace/trace_functions_graph.c:901:23: warning: variable 'func' set but not used [-Wunused-but-set-variable]
     901 |         unsigned long func;
         |                       ^~~~


vim +22 include/linux/ftrace_regs.h

e4cf33ca48128d Steven Rostedt            2024-10-10  18  
e4cf33ca48128d Steven Rostedt            2024-10-10  19  #define ftrace_regs_get_instruction_pointer(fregs) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15  20) 	instruction_pointer(&arch_ftrace_regs(fregs)->regs)
e4cf33ca48128d Steven Rostedt            2024-10-10  21  #define ftrace_regs_get_argument(fregs, n) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15 @22) 	regs_get_kernel_argument(&arch_ftrace_regs(fregs)->regs, n)
e4cf33ca48128d Steven Rostedt            2024-10-10  23  #define ftrace_regs_get_stack_pointer(fregs) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15  24) 	kernel_stack_pointer(&arch_ftrace_regs(fregs)->regs)
2d17932da44fdc Masami Hiramatsu (Google  2024-10-15  25) #define ftrace_regs_get_return_value(fregs) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15  26) 	regs_return_value(&arch_ftrace_regs(fregs)->regs)
e4cf33ca48128d Steven Rostedt            2024-10-10  27  #define ftrace_regs_set_return_value(fregs, ret) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15  28) 	regs_set_return_value(&arch_ftrace_regs(fregs)->regs, ret)
e4cf33ca48128d Steven Rostedt            2024-10-10  29  #define ftrace_override_function_with_return(fregs) \
0b582611a8f427 Masami Hiramatsu (Google  2024-10-15  30) 	override_function_with_return(&arch_ftrace_regs(fregs)->regs)
e4cf33ca48128d Steven Rostedt            2024-10-10  31  #define ftrace_regs_query_register_offset(name) \
e4cf33ca48128d Steven Rostedt            2024-10-10  32  	regs_query_register_offset(name)
a3ed4157b7d898 Masami Hiramatsu (Google  2024-12-26  33) #define ftrace_regs_get_frame_pointer(fregs) \
a3ed4157b7d898 Masami Hiramatsu (Google  2024-12-26  34) 	frame_pointer(&arch_ftrace_regs(fregs)->regs)
e4cf33ca48128d Steven Rostedt            2024-10-10  35  

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-02-27 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 22:26 [PATCH v3 0/4] ftrace: Add function arguments to function tracers Steven Rostedt
2025-02-25 22:26 ` [PATCH v3 1/4] ftrace: Add print_function_args() Steven Rostedt
2025-02-26 14:48   ` Masami Hiramatsu
2025-02-25 22:26 ` [PATCH v3 2/4] ftrace: Add support for function argument to graph tracer Steven Rostedt
2025-02-26 14:48   ` Masami Hiramatsu
2025-02-26 16:11     ` Steven Rostedt
2025-02-27 14:00   ` kernel test robot [this message]
2025-02-27 15:13     ` Steven Rostedt
2025-02-25 22:26 ` [PATCH v3 3/4] ftrace: Have funcgraph-args take affect during tracing Steven Rostedt
2025-02-25 22:26 ` [PATCH v3 4/4] ftrace: Add arguments to function tracer Steven Rostedt
2025-02-27 16:32   ` kernel test robot
2025-02-27 16:45     ` Steven Rostedt

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=202502272155.zS8WsTRz-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.