From: kbuild test robot <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andi Kleen <ak@linux.intel.com>
Subject: [linux-next:master 5963/5971] futex.c:undefined reference to `__arch_atomic_add_unless'
Date: Thu, 30 Mar 2017 09:11:56 +0800 [thread overview]
Message-ID: <201703300952.VVHcc8hB%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --]
Hi Andrew,
It's probably a bug fix that unveils the link errors.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8f8ab14f4414e1be0e7c23036017e3e3130ba7cd
commit: 2ef5da008877ad2222e9a8964d39cf50fd2236d7 [5963/5971] x86-atomic-move-__atomic_add_unless-out-of-line-fix
config: um-alldefconfig (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
git checkout 2ef5da008877ad2222e9a8964d39cf50fd2236d7
# save the attached .config to linux build tree
make ARCH=um
All errors (new ones prefixed by >>):
kernel/built-in.o: In function `get_task_cred':
(.text+0x23d34): undefined reference to `__arch_atomic_add_unless'
kernel/built-in.o: In function `atomic_dec_and_mutex_lock':
(.text+0x2f166): undefined reference to `__arch_atomic_add_unless'
kernel/built-in.o: In function `get_pi_state':
>> futex.c:(.text+0x4b1c1): undefined reference to `__arch_atomic_add_unless'
kernel/built-in.o: In function `get_futex_key':
futex.c:(.text+0x4ba2a): undefined reference to `__arch_atomic_add_unless'
mm/built-in.o: In function `oom_reaper':
>> oom_kill.c:(.text+0x4b36): undefined reference to `__arch_atomic_add_unless'
mm/built-in.o:(.text+0x10e01): more undefined references to `__arch_atomic_add_unless' follow
collect2: error: ld returned 1 exit status
---
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: 4437 bytes --]
reply other threads:[~2017-03-30 1:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201703300952.VVHcc8hB%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--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