From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-6.1 11/12] ld.lld: error: undefined symbol: __tracepoint_cros_vfs_rename_exit
Date: Tue, 19 Nov 2024 12:30:20 +0800 [thread overview]
Message-ID: <202411191208.G62uoepD-lkp@intel.com> (raw)
tree: https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-6.1
head: 88ae4c0585c1cbf6bcc0d9aeadb3e8f207530c9f
commit: a6725d3a987f03c22ed97a67a8ab6b5c63243807 [11/12] CHROMIUM: add cros file rename tracepoints for bpf
config: arm64-randconfig-001-20241118 (https://download.01.org/0day-ci/archive/20241119/202411191208.G62uoepD-lkp@intel.com/config)
compiler: clang version 14.0.6 (https://github.com/llvm/llvm-project f28c006a5895fc0e329fe15fead81e37457cb1d1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241119/202411191208.G62uoepD-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/202411191208.G62uoepD-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: __traceiter_cros_vfs_rename_exit
>>> referenced by cros_file.h:68 (include/trace/events/cros_file.h:68)
>>> fs/namei.o:(vfs_rename) in archive vmlinux.a
>>> referenced by cros_file.h:68 (include/trace/events/cros_file.h:68)
>>> fs/namei.o:(vfs_rename) in archive vmlinux.a
>>> referenced by cros_file.h:68 (include/trace/events/cros_file.h:68)
>>> fs/namei.o:(vfs_rename) in archive vmlinux.a
>>> referenced 3 more times
--
>> ld.lld: error: undefined symbol: __tracepoint_cros_vfs_rename_exit
>>> referenced by namei.c
>>> fs/namei.o:(__jump_table+0x8) in archive vmlinux.a
>>> referenced by namei.c
>>> fs/namei.o:(__jump_table+0x18) in archive vmlinux.a
>>> referenced by namei.c
>>> fs/namei.o:(__jump_table+0x28) in archive vmlinux.a
>>> referenced 3 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-11-19 4: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=202411191208.G62uoepD-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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 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.