From: kbuild test robot <fengguang.wu@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com, Ingo Molnar <mingo@kernel.org>
Subject: [tip:x86/asm 3/3] lib/bug.c:135: undefined reference to `__start___bug_table'
Date: Thu, 30 Mar 2017 21:02:31 +0800 [thread overview]
Message-ID: <201703302127.s9kml8XH%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1929 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/asm
head: 19d436268dde95389c616bb3819da73f0a8b28a8
commit: 19d436268dde95389c616bb3819da73f0a8b28a8 [3/3] debug: Add _ONCE() logic to report_bug()
config: arm-efm32_defconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705
reproduce:
wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 19d436268dde95389c616bb3819da73f0a8b28a8
# save the attached .config to linux build tree
make.cross ARCH=arm
All errors (new ones prefixed by >>):
lib/lib.a(bug.o): In function `find_bug':
>> lib/bug.c:135: undefined reference to `__start___bug_table'
>> lib/bug.c:135: undefined reference to `__stop___bug_table'
vim +135 lib/bug.c
7664c5a1 Jeremy Fitzhardinge 2006-12-08 129 #endif
7664c5a1 Jeremy Fitzhardinge 2006-12-08 130
19d43626 Peter Zijlstra 2017-02-25 131 struct bug_entry *find_bug(unsigned long bugaddr)
7664c5a1 Jeremy Fitzhardinge 2006-12-08 132 {
19d43626 Peter Zijlstra 2017-02-25 133 struct bug_entry *bug;
7664c5a1 Jeremy Fitzhardinge 2006-12-08 134
7664c5a1 Jeremy Fitzhardinge 2006-12-08 @135 for (bug = __start___bug_table; bug < __stop___bug_table; ++bug)
b93a531e Jan Beulich 2008-12-16 136 if (bugaddr == bug_addr(bug))
7664c5a1 Jeremy Fitzhardinge 2006-12-08 137 return bug;
7664c5a1 Jeremy Fitzhardinge 2006-12-08 138
:::::: The code at line 135 was first introduced by commit
:::::: 7664c5a1da4711bb6383117f51b94c8dc8f3f1cd [PATCH] Generic BUG implementation
:::::: TO: Jeremy Fitzhardinge <jeremy@goop.org>
:::::: CC: Linus Torvalds <torvalds@woody.osdl.org>
---
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: 11202 bytes --]
next reply other threads:[~2017-03-30 13:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 13:02 kbuild test robot [this message]
2017-03-30 15:49 ` Peter Zijlstra
2017-03-30 15:53 ` Peter Zijlstra
2017-03-31 0:27 ` Fengguang Wu
2017-04-03 8:27 ` [tip:x86/asm] debug: Fix __bug_table[] in arch linker scripts tip-bot for Peter Zijlstra
2017-04-03 9:57 ` hpa
2017-04-03 12:25 ` Peter Zijlstra
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=201703302127.s9kml8XH%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tipbuild@zytor.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
all inboxes | Powered by JetHome®