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 v5 2/2] extable: verify address is read-only Date: Fri, 7 Apr 2017 01:41:26 +0800 [thread overview] Message-ID: <201704070155.EM9TWkdW%fengguang.wu@intel.com> (raw) In-Reply-To: <20170406033550.32525-3-ewk@edkovsky.org> [-- Attachment #1: Type: text/plain, Size: 1741 bytes --] Hi Eddie, [auto build test ERROR on next-20170330] [cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc5] [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/20170407-004322 config: i386-randconfig-x010-201714 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>): kernel/extable.c: In function 'core_kernel_rodata': >> kernel/extable.c:169:29: error: '__start_ro_after_init' undeclared (first use in this function) if (addr >= (unsigned long)__start_ro_after_init && ^~~~~~~~~~~~~~~~~~~~~ kernel/extable.c:169:29: note: each undeclared identifier is reported only once for each function it appears in >> kernel/extable.c:170:28: error: '__end_ro_after_init' undeclared (first use in this function) addr < (unsigned long)__end_ro_after_init) ^~~~~~~~~~~~~~~~~~~ vim +/__start_ro_after_init +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_ro_after_init && > 170 addr < (unsigned long)__end_ro_after_init) 171 return 1; 172 173 return 0; --- 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: 27264 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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: [kernel-hardening] Re: [PATCH v5 2/2] extable: verify address is read-only Date: Fri, 7 Apr 2017 01:41:26 +0800 [thread overview] Message-ID: <201704070155.EM9TWkdW%fengguang.wu@intel.com> (raw) In-Reply-To: <20170406033550.32525-3-ewk@edkovsky.org> [-- Attachment #1: Type: text/plain, Size: 1741 bytes --] Hi Eddie, [auto build test ERROR on next-20170330] [cannot apply to linus/master linux/master jeyu/modules-next v4.9-rc8 v4.9-rc7 v4.9-rc6 v4.11-rc5] [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/20170407-004322 config: i386-randconfig-x010-201714 (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901 reproduce: # save the attached .config to linux build tree make ARCH=i386 All errors (new ones prefixed by >>): kernel/extable.c: In function 'core_kernel_rodata': >> kernel/extable.c:169:29: error: '__start_ro_after_init' undeclared (first use in this function) if (addr >= (unsigned long)__start_ro_after_init && ^~~~~~~~~~~~~~~~~~~~~ kernel/extable.c:169:29: note: each undeclared identifier is reported only once for each function it appears in >> kernel/extable.c:170:28: error: '__end_ro_after_init' undeclared (first use in this function) addr < (unsigned long)__end_ro_after_init) ^~~~~~~~~~~~~~~~~~~ vim +/__start_ro_after_init +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_ro_after_init && > 170 addr < (unsigned long)__end_ro_after_init) 171 return 1; 172 173 return 0; --- 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: 27264 bytes --]
next prev parent reply other threads:[~2017-04-06 17:42 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-04-06 3:35 [PATCH v5 0/2] provide check for ro_after_init memory sections Eddie Kovsky 2017-04-06 3:35 ` [kernel-hardening] " Eddie Kovsky 2017-04-06 3:35 ` [PATCH v5 1/2] module: verify address is read-only Eddie Kovsky 2017-04-06 3:35 ` [kernel-hardening] " Eddie Kovsky 2017-04-07 1:58 ` Jessica Yu 2017-04-07 1:58 ` [kernel-hardening] " Jessica Yu 2017-04-07 20:46 ` Kees Cook 2017-04-07 20:46 ` [kernel-hardening] " Kees Cook 2017-04-06 3:35 ` [PATCH v5 2/2] extable: " Eddie Kovsky 2017-04-06 3:35 ` [kernel-hardening] " Eddie Kovsky 2017-04-06 17:20 ` kbuild test robot 2017-04-06 17:20 ` [kernel-hardening] " kbuild test robot 2017-04-06 17:41 ` kbuild test robot [this message] 2017-04-06 17:41 ` kbuild test robot 2017-04-07 19:29 ` Eddie Kovsky 2017-04-07 19:29 ` [kernel-hardening] " Eddie Kovsky 2017-04-07 20:45 ` Kees Cook 2017-04-07 20:45 ` [kernel-hardening] " Kees Cook 2017-04-07 21:53 ` [PATCH v5 0/2] provide check for ro_after_init memory sections Kees Cook 2017-04-07 21:53 ` [kernel-hardening] " Kees Cook 2017-04-07 22:12 ` Andrew Morton 2017-04-07 22:12 ` [kernel-hardening] " Andrew Morton 2017-04-07 22:15 ` Kees Cook 2017-04-07 22:15 ` [kernel-hardening] " Kees Cook 2017-04-07 22:23 ` Andrew Morton 2017-04-07 22:23 ` [kernel-hardening] " Andrew Morton 2017-04-07 22:47 ` Kees Cook 2017-04-07 22:47 ` [kernel-hardening] " 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=201704070155.EM9TWkdW%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: linkBe 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.