From: kbuild test robot <lkp@intel.com>
To: Christophe Leroy <christophe.leroy@c-s.fr>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
Michael Ellerman <mpe@ellerman.id.au>
Subject: WARNING: vmlinux.o(.text+0x21a7c): Section mismatch in reference from the function mmu_mark_rodata_ro() to the function .init.text:mmu_mapin_ram_chunk()
Date: Sat, 14 Dec 2019 07:46:43 +0800 [thread overview]
Message-ID: <201912140717.kl0Cju7j%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 37d4e84f765bb3038ddfeebdc5d1cfd7e1ef688f
commit: a2227a27774328507a5c2335a6dd600c079d1ff5 powerpc/32: Don't populate page tables for block mapped pages except on the 8xx.
date: 4 weeks ago
config: powerpc-randconfig-a001-20191213 (attached as .config)
compiler: powerpc-linux-gcc (GCC) 7.5.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout a2227a27774328507a5c2335a6dd600c079d1ff5
# save the attached .config to linux build tree
GCC_VERSION=7.5.0 make.cross ARCH=powerpc
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> WARNING: vmlinux.o(.text+0x21a7c): Section mismatch in reference from the function mmu_mark_rodata_ro() to the function .init.text:mmu_mapin_ram_chunk()
The function mmu_mark_rodata_ro() references
the function __init mmu_mapin_ram_chunk().
This is often because mmu_mark_rodata_ro lacks a __init
annotation or the annotation of mmu_mapin_ram_chunk is wrong.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 26416 bytes --]
reply other threads:[~2019-12-13 23:48 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=201912140717.kl0Cju7j%lkp@intel.com \
--to=lkp@intel.com \
--cc=christophe.leroy@c-s.fr \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
/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
all inboxes | Powered by JetHome®