From: kernel test robot <lkp@intel.com>
To: Johannes Berg <johannes@sipsolutions.net>, linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
linux-trace-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: [PATCH v3 1/4] tracing: add __print_sym() to replace __print_symbolic()
Date: Fri, 7 Jun 2024 21:27:00 +0800 [thread overview]
Message-ID: <202406072129.3ZzFDOlC-lkp@intel.com> (raw)
In-Reply-To: <20240606203255.49433-7-johannes@sipsolutions.net>
Hi Johannes,
kernel test robot noticed the following build errors:
[auto build test ERROR on mcgrof/modules-next]
[also build test ERROR on arnd-asm-generic/master tip/timers/core net/main net-next/main linus/master horms-ipvs/master v6.10-rc2 next-20240607]
[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/Johannes-Berg/tracing-add-__print_sym-to-replace-__print_symbolic/20240607-043503
base: https://git.kernel.org/pub/scm/linux/kernel/git/mcgrof/linux.git modules-next
patch link: https://lore.kernel.org/r/20240606203255.49433-7-johannes%40sipsolutions.net
patch subject: [PATCH v3 1/4] tracing: add __print_sym() to replace __print_symbolic()
config: arc-randconfig-002-20240607 (https://download.01.org/0day-ci/archive/20240607/202406072129.3ZzFDOlC-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/20240607/202406072129.3ZzFDOlC-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/202406072129.3ZzFDOlC-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/trace/trace_events.c: In function 'show_sym_list':
>> kernel/trace/trace_events.c:1586:31: error: invalid use of undefined type 'struct module'
1586 | sym_defs = mod->trace_sym_defs;
| ^~
kernel/trace/trace_events.c:1587:33: error: invalid use of undefined type 'struct module'
1587 | n_sym_defs = mod->num_trace_sym_defs;
| ^~
vim +1586 kernel/trace/trace_events.c
1575
1576 /* note: @name is not NUL-terminated */
1577 static void show_sym_list(struct seq_file *m, struct trace_event_call *call,
1578 const char *name, unsigned int name_len)
1579 {
1580 struct trace_sym_def **sym_defs;
1581 unsigned int n_sym_defs, i;
1582
1583 if (call->module) {
1584 struct module *mod = call->module;
1585
> 1586 sym_defs = mod->trace_sym_defs;
1587 n_sym_defs = mod->num_trace_sym_defs;
1588 } else {
1589 sym_defs = __start_ftrace_sym_defs;
1590 n_sym_defs = __stop_ftrace_sym_defs - __start_ftrace_sym_defs;
1591 }
1592
1593 for (i = 0; i < n_sym_defs; i++) {
1594 unsigned int sym_len;
1595
1596 if (!sym_defs[i])
1597 continue;
1598 if (sym_defs[i]->system != call->class->system)
1599 continue;
1600 sym_len = strlen(sym_defs[i]->symbol_id);
1601 if (name_len != sym_len)
1602 continue;
1603 if (strncmp(sym_defs[i]->symbol_id, name, sym_len))
1604 continue;
1605 if (sym_defs[i]->show)
1606 sym_defs[i]->show(m);
1607 break;
1608 }
1609 }
1610
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-06-07 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-06 20:32 [PATCH v3 0/4] tracing: improve symbolic printing Johannes Berg
2024-06-06 20:32 ` [PATCH v3 1/4] tracing: add __print_sym() to replace __print_symbolic() Johannes Berg
2024-06-07 13:27 ` kernel test robot [this message]
2024-06-07 13:37 ` kernel test robot
2024-06-06 20:32 ` [PATCH v3 2/4] tracing/timer: use __print_sym() Johannes Berg
2024-06-06 20:32 ` [PATCH v3 3/4] net: dropreason: use new __print_sym() in tracing Johannes Berg
2024-06-06 20:32 ` [PATCH v3 4/4] net: drop_monitor: use drop_reason_lookup() Johannes Berg
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=202406072129.3ZzFDOlC-lkp@intel.com \
--to=lkp@intel.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).