From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [kees:kspp/memcpy/next-20210618/v0 59/82] misc.c:undefined reference to `fortify_warn_write'
Date: Sat, 19 Jun 2021 22:45:59 +0800 [thread overview]
Message-ID: <202106192254.BiOfgemU-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git kspp/memcpy/next-20210618/v0
head: fd2aa2a169de8bde9502e7a2fc48cd03d4bfd996
commit: b44eff85708d836f39515789c036c5003dc34ec6 [59/82] fortify: Detect struct member overflows in memmove()
config: i386-randconfig-a011-20210619 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git/commit/?id=b44eff85708d836f39515789c036c5003dc34ec6
git remote add kees https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git
git fetch --no-tags kees kspp/memcpy/next-20210618/v0
git checkout b44eff85708d836f39515789c036c5003dc34ec6
# save the attached .config to linux build tree
make W=1 ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
ld: arch/x86/boot/compressed/misc.o: in function `.L221':
>> misc.c:(.text+0x17bc): undefined reference to `fortify_warn_write'
ld: arch/x86/boot/compressed/misc.o: in function `bcj_flush':
misc.c:(.text+0x18b0): undefined reference to `fortify_warn_write'
ld: arch/x86/boot/compressed/vmlinux: hidden symbol `fortify_warn_write' isn't defined
ld: final link failed: bad value
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 46918 bytes --]
reply other threads:[~2021-06-19 14:45 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=202106192254.BiOfgemU-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.