From: kernel test robot <lkp@intel.com>
To: david.laight.linux@gmail.com, Kees Cook <kees@kernel.org>,
linux-hardening@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
David Laight <david.laight.linux@gmail.com>
Subject: Re: [PATCH next 2/3] fortify: Optimise strnlen()
Date: Wed, 1 Apr 2026 08:15:22 +0800 [thread overview]
Message-ID: <202604010835.IWCsUV7z-lkp@intel.com> (raw)
In-Reply-To: <20260330132003.3379-3-david.laight.linux@gmail.com>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on next-20260327]
url: https://github.com/intel-lab-lkp/linux/commits/david-laight-linux-gmail-com/fortify-replace-__compiletime_lessthan-with-statically_true/20260331-041123
base: next-20260327
patch link: https://lore.kernel.org/r/20260330132003.3379-3-david.laight.linux%40gmail.com
patch subject: [PATCH next 2/3] fortify: Optimise strnlen()
config: x86_64-buildonly-randconfig-001-20260331 (https://download.01.org/0day-ci/archive/20260401/202604010835.IWCsUV7z-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260401/202604010835.IWCsUV7z-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202604010835.IWCsUV7z-lkp@intel.com/
All errors (new ones prefixed by >>):
>> ld.lld: error: undefined symbol: __fortify_undefined
>>> referenced by fortify-string.h:290 (include/linux/fortify-string.h:290)
>>> vmlinux.o:(parse_early_param)
>>> referenced by fortify-string.h:218 (include/linux/fortify-string.h:218)
>>> vmlinux.o:(parse_early_param)
>>> referenced by fortify-string.h:290 (include/linux/fortify-string.h:290)
>>> vmlinux.o:(setup_boot_config)
>>> referenced 2103 more times
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next parent reply other threads:[~2026-04-01 0:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260330132003.3379-3-david.laight.linux@gmail.com>
2026-04-01 0:15 ` kernel test robot [this message]
2026-04-03 8:23 ` [PATCH next 2/3] fortify: Optimise strnlen() David Laight
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=202604010835.IWCsUV7z-lkp@intel.com \
--to=lkp@intel.com \
--cc=david.laight.linux@gmail.com \
--cc=kees@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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