From: kernel test robot <lkp@intel.com>
To: Sven Schnelle <svens@linux.ibm.com>
Cc: oe-kbuild-all@lists.linux.dev, Jiri Olsa <jolsa@kernel.org>,
"Steven Rostedt (Google)" <rostedt@goodmis.org>
Subject: [jolsa-perf:tmp 5/5] kernel/trace/trace_output.c:1110:26: error: 'FTRACE_REGS_MAX_ARGS' undeclared
Date: Wed, 1 Jan 2025 09:30:27 +0800 [thread overview]
Message-ID: <202501010955.Js0ZSSjD-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git tmp
head: e2a63411ac4e1b7b36da9f4c2245570d92842d2e
commit: e2a63411ac4e1b7b36da9f4c2245570d92842d2e [5/5] ftrace: Add arguments to function tracer
config: arc-randconfig-001-20250101 (https://download.01.org/0day-ci/archive/20250101/202501010955.Js0ZSSjD-lkp@intel.com/config)
compiler: arc-elf-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250101/202501010955.Js0ZSSjD-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/202501010955.Js0ZSSjD-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace_output.c: In function 'trace_fn_trace':
>> kernel/trace/trace_output.c:1110:26: error: 'FTRACE_REGS_MAX_ARGS' undeclared (first use in this function)
1110 | if (args_size >= FTRACE_REGS_MAX_ARGS * sizeof(long))
| ^~~~~~~~~~~~~~~~~~~~
kernel/trace/trace_output.c:1110:26: note: each undeclared identifier is reported only once for each function it appears in
--
kernel/trace/trace.c: In function 'trace_function':
>> kernel/trace/trace.c:2907:17: error: 'FTRACE_REGS_MAX_ARGS' undeclared (first use in this function)
2907 | size += FTRACE_REGS_MAX_ARGS * !!fregs * sizeof(long);
| ^~~~~~~~~~~~~~~~~~~~
kernel/trace/trace.c:2907:17: note: each undeclared identifier is reported only once for each function it appears in
>> kernel/trace/trace.c:2919:42: error: implicit declaration of function 'ftrace_regs_get_argument' [-Werror=implicit-function-declaration]
2919 | entry->args[i] = ftrace_regs_get_argument(fregs, i);
| ^~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/FTRACE_REGS_MAX_ARGS +1110 kernel/trace/trace_output.c
1097
1098 /* TRACE_FN */
1099 static enum print_line_t trace_fn_trace(struct trace_iterator *iter, int flags,
1100 struct trace_event *event)
1101 {
1102 struct ftrace_entry *field;
1103 struct trace_seq *s = &iter->seq;
1104 unsigned long *args;
1105 int args_size;
1106
1107 trace_assign_type(field, iter->ent);
1108
1109 args_size = iter->ent_size - offsetof(struct ftrace_entry, args);
> 1110 if (args_size >= FTRACE_REGS_MAX_ARGS * sizeof(long))
1111 args = field->args;
1112 else
1113 args = NULL;
1114
1115 print_fn_trace(s, field->ip, field->parent_ip, iter->tr->text_delta,
1116 args, flags);
1117 trace_seq_putc(s, '\n');
1118
1119 return trace_handle_return(s);
1120 }
1121
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-01-01 1:31 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=202501010955.Js0ZSSjD-lkp@intel.com \
--to=lkp@intel.com \
--cc=jolsa@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=svens@linux.ibm.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 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.