From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Mel Gorman <mgorman@suse.de>,
Thomas Garnier <thgarnie@google.com>,
Kees Cook <keescook@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [mel:mm-vmscan-node-lru-v7r3 38/200] slub.c:undefined reference to `cache_random_seq_create'
Date: Tue, 14 Jun 2016 03:37:57 +0800 [thread overview]
Message-ID: <201606140353.WeDaHl1M%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 950 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mel/linux mm-vmscan-node-lru-v7r3
head: 276a5614a25ce20248f42bd4fb025b80ae0c9be1
commit: 44c61fe5d7f13025a2a1f6efbbc0da75ad93ee19 [38/200] mm: SLUB freelist randomization
config: x86_64-randconfig-x018-06140033 (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
git checkout 44c61fe5d7f13025a2a1f6efbbc0da75ad93ee19
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
mm/built-in.o: In function `init_cache_random_seq':
>> slub.c:(.text+0x507dc): undefined reference to `cache_random_seq_create'
mm/built-in.o: In function `__kmem_cache_release':
>> (.text+0x53979): undefined reference to `cache_random_seq_destroy'
---
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: 21401 bytes --]
next reply other threads:[~2016-06-13 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 19:37 kbuild test robot [this message]
2016-06-13 21:11 ` Andrew Morton
2016-06-13 23:51 ` Kees Cook
2016-06-15 17:43 ` Kees Cook
2016-06-15 21:26 ` Andrew Morton
2016-06-15 22:37 ` Kees Cook
2016-06-15 22:44 ` Andrew Morton
2016-06-15 22:53 ` 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=201606140353.WeDaHl1M%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@01.org \
--cc=keescook@chromium.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=thgarnie@google.com \
/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