mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Eddie Kovsky <ewk@edkovsky.org>
Cc: kbuild-all@01.org, jeyu@redhat.com, rusty@rustcorp.com.au,
	keescook@chromium.org, linux-kernel@vger.kernel.org,
	kernel-hardening@lists.openwall.com
Subject: Re: [PATCH v4 2/2] extable: verify address is read-only
Date: Mon, 27 Mar 2017 16:43:05 +0800	[thread overview]
Message-ID: <201703271633.xbYHmB37%fengguang.wu@intel.com> (raw)
In-Reply-To: <20170326210825.23255-3-ewk@edkovsky.org>

[-- Attachment #1: Type: text/plain, Size: 1941 bytes --]

Hi Eddie,

[auto build test ERROR on next-20170323]
[cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc4]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Eddie-Kovsky/module-verify-address-is-read-only/20170327-142922
config: blackfin-BF561-EZKIT-SMP_defconfig (attached as .config)
compiler: bfin-uclinux-gcc (GCC) 6.2.0
reproduce:
        wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # save the attached .config to linux build tree
        make.cross ARCH=blackfin 

All errors (new ones prefixed by >>):

   kernel/built-in.o: In function `core_kernel_rodata':
>> kernel/extable.c:169: undefined reference to `__start_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__start_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__end_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__end_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__start_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__start_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__end_data_ro_after_init'
>> kernel/extable.c:169: undefined reference to `__end_data_ro_after_init'

vim +169 kernel/extable.c

   163	int core_kernel_rodata(unsigned long addr)
   164	{
   165		if (addr >= (unsigned long)__start_rodata &&
   166		    addr < (unsigned long)__end_rodata)
   167			return 1;
   168	
 > 169		if (addr >= (unsigned long)__start_data_ro_after_init &&
   170		    addr < (unsigned long)__end_data_ro_after_init)
   171			return 1;
   172	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 10729 bytes --]

  reply	other threads:[~2017-03-27  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26 21:08 [PATCH v4 0/2] provide check for ro_after_init memory sections Eddie Kovsky
2017-03-26 21:08 ` [PATCH v4 1/2] module: verify address is read-only Eddie Kovsky
2017-03-30  3:31   ` Jessica Yu
2017-03-26 21:08 ` [PATCH v4 2/2] extable: " Eddie Kovsky
2017-03-27  8:43   ` kbuild test robot [this message]
2017-03-27 18:42     ` Kees Cook
2017-03-29  3:28       ` Eddie Kovsky
2017-03-30  3:27         ` Jessica Yu
2017-03-30 16:24           ` Kees Cook
2017-03-31  3:09             ` Eddie Kovsky
2017-04-03 22:10           ` Kees Cook

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=201703271633.xbYHmB37%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=ewk@edkovsky.org \
    --cc=jeyu@redhat.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=kernel-hardening@lists.openwall.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.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®