From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <fengguang.wu@intel.com>
Cc: Eddie Kovsky <ewk@edkovsky.org>,
kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [mmotm:master 161/276] kernel/extable.c:174: undefined reference to `__start_ro_after_init'
Date: Mon, 10 Apr 2017 14:09:55 -0700 [thread overview]
Message-ID: <20170410140955.5a82e6f0fcb784c03ddd305c@linux-foundation.org> (raw)
In-Reply-To: <201704081021.kBB1nNuC%fengguang.wu@intel.com>
On Sat, 8 Apr 2017 10:37:22 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
> tree: git://git.cmpxchg.org/linux-mmotm.git master
> head: 5b220005fda0593464fc4549eea586e597bf783c
> commit: 7c61156608a0054d57061bd154b1ac537c49e0a8 [161/276] extable: verify address is read-only
> config: arm-efm32_defconfig (attached as .config)
> compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
> reproduce:
> wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 7c61156608a0054d57061bd154b1ac537c49e0a8
> # save the attached .config to linux build tree
> make.cross ARCH=arm
>
> All errors (new ones prefixed by >>):
>
> kernel/built-in.o: In function `core_kernel_rodata':
> >> kernel/extable.c:174: undefined reference to `__start_ro_after_init'
> >> kernel/extable.c:174: undefined reference to `__end_ro_after_init'
Thanks, I dropped the patch. And its companion
module-verify-address-is-read-only.patch to keep things tidy.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-04-10 21:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 2:37 kbuild test robot
2017-04-10 21:09 ` Andrew Morton [this message]
2017-04-10 23:54 ` Stephen Rothwell
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=20170410140955.5a82e6f0fcb784c03ddd305c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=ewk@edkovsky.org \
--cc=fengguang.wu@intel.com \
--cc=hannes@cmpxchg.org \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.org \
--cc=sfr@canb.auug.org.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