All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH v3] [RFC] trace: Add kprobe on tracepoint
Date: Wed, 11 Aug 2021 15:19:47 +0800	[thread overview]
Message-ID: <202108111551.tWhU0FJ2-lkp@intel.com> (raw)
In-Reply-To: <20210811030348.1791207-1-tz.stoyanov@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 4148 bytes --]

Hi "Tzvetomir,

[FYI, it's a private test report for your RFC patch.]
[auto build test ERROR on v5.14-rc5]
[also build test ERROR on next-20210810]
[cannot apply to tip/perf/core]
[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]

url:    https://github.com/0day-ci/linux/commits/Tzvetomir-Stoyanov-VMware/trace-Add-kprobe-on-tracepoint/20210811-110525
base:    36a21d51725af2ce0700c6ebcb6b9594aac658a6
config: microblaze-randconfig-c023-20210811 (attached as .config)
compiler: microblaze-linux-gcc (GCC) 10.3.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/1c1c02a4ad23d5bbc4c2de9dfd125e3be33de636
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Tzvetomir-Stoyanov-VMware/trace-Add-kprobe-on-tracepoint/20210811-110525
        git checkout 1c1c02a4ad23d5bbc4c2de9dfd125e3be33de636
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-10.3.0 make.cross O=build_dir ARCH=microblaze SHELL=/bin/bash

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `eprobe_dyn_event_create':
   (.text+0x290): undefined reference to `trace_probe_create'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `kprobe_event_define_fields':
   (.text+0x324): undefined reference to `traceprobe_define_arg_fields'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `alloc_event_probe':
   (.text+0x41c): undefined reference to `trace_probe_init'
>> microblaze-linux-ld: (.text+0x474): undefined reference to `trace_probe_cleanup'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `enable_trace_eprobe':
   (.text+0x130c): undefined reference to `trace_probe_add_file'
   microblaze-linux-ld: (.text+0x1520): undefined reference to `trace_probe_remove_file'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `eprobe_register':
   (.text+0x15fc): undefined reference to `trace_probe_get_file_link'
   microblaze-linux-ld: (.text+0x1638): undefined reference to `trace_probe_remove_file'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `unregister_trace_eprobe':
   (.text+0x17c8): undefined reference to `trace_probe_unlink'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `eprobe_dyn_event_match':
   (.text+0x19c8): undefined reference to `trace_probe_match_command_args'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `eprobe_dyn_event_release':
   (.text+0x1b3c): undefined reference to `trace_probe_cleanup'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `__trace_eprobe_create':
   (.text+0x1c2c): undefined reference to `trace_probe_log_init'
   microblaze-linux-ld: (.text+0x1c6c): undefined reference to `traceprobe_parse_event_name'
   microblaze-linux-ld: (.text+0x1f2c): undefined reference to `traceprobe_parse_event_name'
   microblaze-linux-ld: (.text+0x22d0): undefined reference to `traceprobe_parse_probe_arg'
   microblaze-linux-ld: (.text+0x2318): undefined reference to `traceprobe_set_print_fmt'
   microblaze-linux-ld: (.text+0x2378): undefined reference to `trace_probe_register_event_call'
>> microblaze-linux-ld: (.text+0x23a8): undefined reference to `dyn_event_list'
   microblaze-linux-ld: (.text+0x2404): undefined reference to `trace_probe_cleanup'
   microblaze-linux-ld: kernel/trace/trace_eprobe.o: in function `trace_events_eprobe_init_early':
   (.init.text+0x14): undefined reference to `dyn_event_register'

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 26947 bytes --]

      parent reply	other threads:[~2021-08-11  7:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  3:03 [PATCH v3] [RFC] trace: Add kprobe on tracepoint Tzvetomir Stoyanov (VMware)
2021-08-11  7:19 ` kernel test robot
2021-08-11  7:19 ` kernel test robot [this message]

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=202108111551.tWhU0FJ2-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.