From: kbuild test robot <lkp@intel.com>
To: Rick Edgecombe <rick.p.edgecombe@intel.com>
Cc: kbuild-all@01.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, kernel-hardening@lists.openwall.com,
daniel@iogearbox.net, jannh@google.com, keescook@chromium.org,
kristen@linux.intel.com, dave.hansen@intel.com,
arjan@linux.intel.com,
Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH v3 2/3] x86/modules: Increase randomization for modules
Date: Thu, 16 Aug 2018 15:15:02 +0800 [thread overview]
Message-ID: <201808161516.1Wjg2efl%fengguang.wu@intel.com> (raw)
In-Reply-To: <1534365020-18943-3-git-send-email-rick.p.edgecombe@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2604 bytes --]
Hi Rick,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180815]
[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/Rick-Edgecombe/KASLR-feature-to-randomize-each-loadable-module/20180816-120750
config: um-x86_64_defconfig (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=um SUBARCH=x86_64
Note: the linux-review/Rick-Edgecombe/KASLR-feature-to-randomize-each-loadable-module/20180816-120750 HEAD 7eff11788897c8579f53bc7043f854794dbad25f builds fine.
It only hurts bisectibility.
All error/warnings (new ones prefixed by >>):
arch/x86/um/../kernel/module.c: In function 'kaslr_randomize_each_module':
>> arch/x86/um/../kernel/module.c:53:9: error: implicit declaration of function 'kaslr_enabled' [-Werror=implicit-function-declaration]
return kaslr_enabled()
^~~~~~~~~~~~~
arch/x86/um/../kernel/module.c: In function 'get_modules_rand_len':
>> arch/x86/um/../kernel/module.c:68:9: error: 'MODULES_RAND_LEN' undeclared (first use in this function); did you mean 'MODULE_NAME_LEN'?
return MODULES_RAND_LEN;
^~~~~~~~~~~~~~~~
MODULE_NAME_LEN
arch/x86/um/../kernel/module.c:68:9: note: each undeclared identifier is reported only once for each function it appears in
>> arch/x86/um/../kernel/module.c:69:1: warning: control reaches end of non-void function [-Wreturn-type]
}
^
cc1: some warnings being treated as errors
vim +/kaslr_enabled +53 arch/x86/um/../kernel/module.c
50
51 static inline int kaslr_randomize_each_module(void)
52 {
> 53 return kaslr_enabled()
54 && IS_ENABLED(CONFIG_RANDOMIZE_BASE)
55 && IS_ENABLED(CONFIG_X86_64);
56 }
57
58 static inline int kaslr_randomize_base(void)
59 {
60 return kaslr_enabled()
61 && IS_ENABLED(CONFIG_RANDOMIZE_BASE)
62 && !IS_ENABLED(CONFIG_X86_64);
63 }
64
65 #ifdef CONFIG_X86_64
66 static inline const unsigned long get_modules_rand_len(void)
67 {
> 68 return MODULES_RAND_LEN;
> 69 }
70 #else
71 static inline const unsigned long get_modules_rand_len(void)
72 {
73 BUILD_BUG();
74 return 0;
75 }
76 #endif
77
---
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: 7635 bytes --]
next prev parent reply other threads:[~2018-08-16 7:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-15 20:30 [PATCH v3 0/3] KASLR feature to randomize each loadable module Rick Edgecombe
2018-08-15 20:30 ` [PATCH v3 1/3] vmalloc: Add __vmalloc_node_try_addr function Rick Edgecombe
2018-08-16 5:01 ` kbuild test robot
2018-08-15 20:30 ` [PATCH v3 2/3] x86/modules: Increase randomization for modules Rick Edgecombe
2018-08-16 7:15 ` kbuild test robot [this message]
2018-08-15 20:30 ` [PATCH v3 3/3] vmalloc: Add debugfs modfraginfo Rick Edgecombe
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=201808161516.1Wjg2efl%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=arjan@linux.intel.com \
--cc=daniel@iogearbox.net \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=kristen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).