All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org, ZhaoLong Wang <wangzhaolong1@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2866/2866] ld.lld: error: undefined symbol: trace_event_buffer_reserve
Date: Mon, 8 Sep 2025 19:11:12 +0800	[thread overview]
Message-ID: <202509081908.rkRF0I49-lkp@intel.com> (raw)

tree:   https://gitee.com/openeuler/kernel.git OLK-6.6
head:   00fccee10860a6b522c55bd4b2f4b40d349c2b52
commit: 1119ec49ac4ac643e6d7c9a5a834040aef87612e [2866/2866] mm, fs: Add BPF_READAHEAD build option for bpf readhead
config: x86_64-buildonly-randconfig-002-20250909 (https://download.01.org/0day-ci/archive/20250908/202509081908.rkRF0I49-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250908/202509081908.rkRF0I49-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/202509081908.rkRF0I49-lkp@intel.com/

All errors (new ones prefixed by >>):

>> ld.lld: error: undefined symbol: trace_event_buffer_reserve
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_level)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_start)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_finish)
   >>> referenced 823 more times
--
>> ld.lld: error: undefined symbol: trace_event_buffer_commit
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_level)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_start)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_initcall_finish)
   >>> referenced 823 more times
--
>> ld.lld: error: undefined symbol: trace_print_bitmask_seq
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_ipi_raise)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_ipi_send_cpumask)
--
>> ld.lld: error: undefined symbol: trace_output_call
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_pm_qos_update_flags)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_802154_rdev_set_short_addr)
--
>> ld.lld: error: undefined symbol: blk_fill_rwbs
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_block_rq_requeue)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(perf_trace_block_rq_requeue)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_event_raw_event_block_rq_completion)
   >>> referenced 13 more times
--
>> ld.lld: error: undefined symbol: trace_print_hex_seq
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_host1x_cdma_push_gather)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_regmap_bulk)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_scsi_dispatch_cmd_start)
   >>> referenced 9 more times
--
>> ld.lld: error: undefined symbol: __tracepoint_devres_log
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(add_dr)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(devres_remove)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(devres_release_all)
   >>> referenced 15 more times
--
>> ld.lld: error: undefined symbol: __SCT__tp_func_devres_log
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(add_dr)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(devres_remove)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(devres_release_all)
   >>> referenced 6 more times
--
>> ld.lld: error: undefined symbol: nvme_trace_disk_name
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_nvme_setup_cmd)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_nvme_complete_rq)
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_nvme_sq)
--
>> ld.lld: error: undefined symbol: nvme_trace_parse_fabrics_cmd
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_nvme_setup_cmd)
--
>> ld.lld: error: undefined symbol: nvme_trace_parse_nvm_cmd
   >>> referenced by usercopy_64.c
   >>>               vmlinux.o:(trace_raw_output_nvme_setup_cmd)
..

Kconfig warnings: (for reference only)
   WARNING: unmet direct dependencies detected for PGP_PRELOAD
   Depends on [n]: CRYPTO [=y] && ASYMMETRIC_KEY_TYPE [=n]
   Selected by [y]:
   - PGP_PRELOAD_PUBLIC_KEYS [=y] && CRYPTO [=y]

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

                 reply	other threads:[~2025-09-08 11:11 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=202509081908.rkRF0I49-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kernel@openeuler.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=wangzhaolong1@huawei.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.