From: kbuild test robot <lkp@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 6276/7050] stackdepot.c:undefined reference to `__softirqentry_text_start'
Date: Wed, 11 Mar 2020 12:31:21 +0800 [thread overview]
Message-ID: <202003111218.5EON5bKp%lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1367 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b86a6a241b7c60ca7a6ca4fb3c0d2aedbbf2c1b6
commit: 2d8fce24a0fb125e4fbbd4bb546cc0f9e6122d8d [6276/7050] kasan: stackdepot: move filter_irq_stacks() to stackdepot.c
config: nds32-randconfig-a001-20200311 (attached as .config)
compiler: nds32le-linux-gcc (GCC) 9.2.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
git checkout 2d8fce24a0fb125e4fbbd4bb546cc0f9e6122d8d
# save the attached .config to linux build tree
GCC_VERSION=9.2.0 make.cross ARCH=nds32
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
nds32le-linux-ld: lib/stackdepot.o: in function `filter_irq_stacks':
>> stackdepot.c:(.text+0x8a): undefined reference to `__softirqentry_text_start'
>> nds32le-linux-ld: stackdepot.c:(.text+0x8e): undefined reference to `__softirqentry_text_start'
>> nds32le-linux-ld: stackdepot.c:(.text+0x92): undefined reference to `__softirqentry_text_end'
nds32le-linux-ld: stackdepot.c:(.text+0x96): undefined reference to `__softirqentry_text_end'
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27527 bytes --]
reply other threads:[~2020-03-11 4:31 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=202003111218.5EON5bKp%lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kbuild-all@lists.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;
as well as URLs for NNTP newsgroup(s).