From: kernel test robot <lkp@intel.com>
To: "Gustavo A. R. Silva" <gustavoars@kernel.org>
Cc: kbuild-all@lists.01.org, linux-leds@vger.kernel.org,
Pavel Machek <pavel@ucw.cz>
Subject: [pavel-linux-leds:for-next 17/17] WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904
Date: Mon, 13 Jul 2020 13:29:35 +0800 [thread overview]
Message-ID: <202007131331.ta5KKp3K%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3128 bytes --]
tree: git://git.kernel.org/pub/scm/linux/kernel/git/pavel/linux-leds.git for-next
head: cf1a1a6a7d81d73bcb5568b23572d6fd593add87
commit: cf1a1a6a7d81d73bcb5568b23572d6fd593add87 [17/17] leds: gpio: Use struct_size() in devm_kzalloc()
config: riscv-randconfig-r012-20200712 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.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
git checkout cf1a1a6a7d81d73bcb5568b23572d6fd593add87
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=riscv
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904
The function ret_from_kernel_thread() references
the variable __init .L904.
This is often because ret_from_kernel_thread lacks a __init
annotation or the annotation of .L904 is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x7c238): Section mismatch in reference from the function profile_tick() to the variable .init.text:.L0
The function profile_tick() references
the variable __init .L0 .
This is often because profile_tick lacks a __init
annotation or the annotation of .L0 is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0xd475de): Section mismatch in reference from the function radeon_audio_init() to the variable .init.text:.LBE12095
The function radeon_audio_init() references
the variable __init .LBE12095.
This is often because radeon_audio_init lacks a __init
annotation or the annotation of .LBE12095 is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x1622c56): Section mismatch in reference from the function netdev_adjacent_change_commit() to the variable .init.text:.L0
The function netdev_adjacent_change_commit() references
the variable __init .L0 .
This is often because netdev_adjacent_change_commit lacks a __init
annotation or the annotation of .L0 is wrong.
--
>> WARNING: modpost: vmlinux.o(.text+0x1622cdc): Section mismatch in reference from the function netdev_adjacent_change_abort() to the variable .init.text:.L0
The function netdev_adjacent_change_abort() references
the variable __init .L0 .
This is often because netdev_adjacent_change_abort lacks a __init
annotation or the annotation of .L0 is wrong.
--
>> WARNING: modpost: vmlinux.o(__ex_table+0x1020): Section mismatch in reference from the (unknown reference) (unknown) to the variable .debug_str:.LASF394
FATAL: modpost: The relocation at __ex_table+0x1020 references
section ".debug_str" which is not executable, IOW
it is not possible for the kernel to fault
at that address. Something is seriously wrong
and should be fixed.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24342 bytes --]
next reply other threads:[~2020-07-13 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 5:29 kernel test robot [this message]
2020-07-13 6:44 ` [pavel-linux-leds:for-next 17/17] WARNING: modpost: vmlinux.o(.text+0x2492): Section mismatch in reference from the function ret_from_kernel_thread() to the variable .init.text:.L904 Pavel Machek
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=202007131331.ta5KKp3K%lkp@intel.com \
--to=lkp@intel.com \
--cc=gustavoars@kernel.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
/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