From: kbuild test robot <fengguang.wu@intel.com>
To: Jason Cooper <jason@lakedaemon.net>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 70/106] arch/x86/kernel/process.c:511:9: error: implicit declaration of function 'randomize_page'
Date: Fri, 12 Aug 2016 09:19:52 +0800 [thread overview]
Message-ID: <201608120949.AtRXkB4G%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1381 bytes --]
tree: git://git.cmpxchg.org/linux-mmotm.git master
head: 304bec1b1d331282b76d92a1487902ce1f158337
commit: 216e0dbb5aab2e588b1f9de3b434015aa1c412f7 [70/106] x86: use simpler API for random address requests
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
git checkout 216e0dbb5aab2e588b1f9de3b434015aa1c412f7
# save the attached .config to linux build tree
make ARCH=i386
Note: the mmotm/master HEAD 304bec1b1d331282b76d92a1487902ce1f158337 builds fine.
It only hurts bisectibility.
All errors (new ones prefixed by >>):
arch/x86/kernel/process.c: In function 'arch_randomize_brk':
>> arch/x86/kernel/process.c:511:9: error: implicit declaration of function 'randomize_page' [-Werror=implicit-function-declaration]
return randomize_page(mm->brk, 0x02000000);
^~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/randomize_page +511 arch/x86/kernel/process.c
505 sp -= get_random_int() % 8192;
506 return sp & ~0xf;
507 }
508
509 unsigned long arch_randomize_brk(struct mm_struct *mm)
510 {
> 511 return randomize_page(mm->brk, 0x02000000);
512 }
513
514 /*
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6373 bytes --]
next reply other threads:[~2016-08-12 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-12 1:19 kbuild test robot [this message]
2016-08-12 1:31 ` Jason Cooper
2016-08-15 21:46 ` Andrew Morton
2016-08-15 22:31 ` Jason Cooper
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=201608120949.AtRXkB4G%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jason@lakedaemon.net \
--cc=kbuild-all@01.org \
--cc=linux-mm@kvack.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