From: Kees Cook <keescook@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild test robot <fengguang.wu@intel.com>,
kbuild-all@01.org, Mel Gorman <mgorman@suse.de>,
Thomas Garnier <thgarnie@google.com>,
Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mel:mm-vmscan-node-lru-v7r3 38/200] slub.c:undefined reference to `cache_random_seq_create'
Date: Mon, 13 Jun 2016 16:51:36 -0700 [thread overview]
Message-ID: <CAGXu5jLH+UzOhPfj5VkydHg=ZxbrQHQe6C1C-dbCBzsAmW9M2Q@mail.gmail.com> (raw)
In-Reply-To: <20160613141123.fcb245b6a7fd3199ae8a32d7@linux-foundation.org>
On Mon, Jun 13, 2016 at 2:11 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Tue, 14 Jun 2016 03:37:57 +0800 kbuild test robot <fengguang.wu@intel.com> wrote:
>
>> 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'
With that config, I get these errors.
> I don't even get that far with that .config. With gcc-4.4.4 I get
>
> init/built-in.o: In function `initcall_blacklisted':
> main.c:(.text+0x41): undefined reference to `__stack_chk_guard'
> main.c:(.text+0xbe): undefined reference to `__stack_chk_guard'
> init/built-in.o: In function `do_one_initcall':
> (.text+0xeb): undefined reference to `__stack_chk_guard'
> init/built-in.o: In function `do_one_initcall':
> (.text+0x22b): undefined reference to `__stack_chk_guard'
> init/built-in.o: In function `name_to_dev_t':
> (.text+0x320): undefined reference to `__stack_chk_guard'
> init/built-in.o:(.text+0x52e): more undefined references to `__stack_chk_guard'
This, I don't. I'm scratching my head about how that's possible. The
__stack_chk_guard is a compiler alias on x86...
> Kees touched it last :)
I'll take a closer look tomorrow...
-Kees
--
Kees Cook
Chrome OS & Brillo Security
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-06-13 23:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 19:37 kbuild test robot
2016-06-13 21:11 ` Andrew Morton
2016-06-13 23:51 ` Kees Cook [this message]
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='CAGXu5jLH+UzOhPfj5VkydHg=ZxbrQHQe6C1C-dbCBzsAmW9M2Q@mail.gmail.com' \
--to=keescook@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.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