From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [peterz-queue:modules/WIP 22/23] ld: kernel/module.c:1033: undefined reference to `ftrace_module_release'
Date: Sat, 30 May 2020 06:08:52 +0800 [thread overview]
Message-ID: <202005300649.o7FGsNtx%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1256 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git modules/WIP
head: cbdf7e5cccc1c668734b1471c56dada830756b97
commit: ee6f5b0a6105ea69816fcec80cba536cdfa47546 [22/23] ftrace: Merge ftrace_module_{init,enable}()
config: x86_64-rhel (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout ee6f5b0a6105ea69816fcec80cba536cdfa47546
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>, old ones prefixed by <<):
ld: kernel/module.o: in function `__do_sys_delete_module':
kernel/module.c:1033: undefined reference to `ftrace_module_release'
>> ld: kernel/module.c:1033: undefined reference to `ftrace_module_release'
ld: kernel/module.o: in function `do_init_module':
kernel/module.c:3641: undefined reference to `ftrace_module_release'
ld: kernel/module.o: in function `load_module':
kernel/module.c:3936: undefined reference to `ftrace_module_release'
---
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: 44820 bytes --]
reply other threads:[~2020-05-29 22:08 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=202005300649.o7FGsNtx%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.