From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5D7D63211; Thu, 6 Apr 2023 11:21:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680780061; x=1712316061; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=MXRWgeeeuucicATdvWXdJpi4j7VRWmOq+LFsppDD6zQ=; b=QMvNfontuoxMTnlqhUM6O2dqHzz+IDOpwbOrrUTidjzJUH9Z7ayN3Y32 nMbeyqy7E7hJtLvzjg7GImyCJaN8KFsNXQZ9A3KTnj4m5WQf2NZXjPAoD UEZp52l4zrqHERNzaV+Bzekkr/MRHOu3dO2Itf9UFbIlBFHyXzOWtReDo ovQVlDLt0u3NNup6K5bPQw/+oL8z1ZuscD0Z5N99QCHGoY23qQR29WpI/ E5c1SPKvJSUfY8qQn8tZPA6XWERPYxi7ITpr468se9GvFEdxMIiR/jJqZ rq432M2/fL0JZRlUnuCUKbwhWqvYCF7euWeo+d/kOhOa2Y5wLtiVw/fvH Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10671"; a="370543800" X-IronPort-AV: E=Sophos;i="5.98,323,1673942400"; d="scan'208";a="370543800" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 06 Apr 2023 04:20:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10671"; a="664406087" X-IronPort-AV: E=Sophos;i="5.98,323,1673942400"; d="scan'208";a="664406087" Received: from lkp-server01.sh.intel.com (HELO b613635ddfff) ([10.239.97.150]) by orsmga006.jf.intel.com with ESMTP; 06 Apr 2023 04:20:49 -0700 Received: from kbuild by b613635ddfff with local (Exim 4.96) (envelope-from ) id 1pkNfc-000RKI-2a; Thu, 06 Apr 2023 11:20:48 +0000 Date: Thu, 6 Apr 2023 19:19:55 +0800 From: kernel test robot To: Kees Cook , linux-hardening@vger.kernel.org Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev, Kees Cook , Andy Shevchenko , Cezary Rojewski , Puyou Lu , Mark Brown , Josh Poimboeuf , Peter Zijlstra , Brendan Higgins , David Gow , Andrew Morton , Linux Memory Management List , Nathan Chancellor , Alexander Potapenko , Zhaoyang Huang , Randy Dunlap , Geert Uytterhoeven , Miguel Ojeda , Nick Desaulniers , Liam Howlett , Vlastimil Babka , Dan Williams , Rasmus Villemoes , Yury Norov , "Jason A. Donenfeld" , Sander Vanheule , Eric Biggers , "Masami Hiramatsu (Google)" , Andrey Konovalov , Linus Walleij Subject: Re: [PATCH 6/9] fortify: Split reporting and avoid passing string pointer Message-ID: <202304061930.4Au0PASm-lkp@intel.com> References: <20230406000212.3442647-6-keescook@chromium.org> Precedence: bulk X-Mailing-List: llvm@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230406000212.3442647-6-keescook@chromium.org> Hi Kees, kernel test robot noticed the following build errors: [auto build test ERROR on kees/for-next/hardening] [also build test ERROR on kees/for-next/pstore kees/for-next/kspp akpm-mm/mm-everything linus/master v6.3-rc5 next-20230406] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/Kees-Cook/kunit-tool-Enable-CONFIG_FORTIFY_SOURCE-under-UML/20230406-081014 base: https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git for-next/hardening patch link: https://lore.kernel.org/r/20230406000212.3442647-6-keescook%40chromium.org patch subject: [PATCH 6/9] fortify: Split reporting and avoid passing string pointer config: arm-randconfig-r025-20230403 (https://download.01.org/0day-ci/archive/20230406/202304061930.4Au0PASm-lkp@intel.com/config) compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 67409911353323ca5edf2049ef0df54132fa1ca7) reproduce (this is a W=1 build): wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # install arm cross compiling tool for clang build # apt-get install binutils-arm-linux-gnueabi # https://github.com/intel-lab-lkp/linux/commit/4fd520e6ee549e1ffe8859e26e57ea64b48e78ea git remote add linux-review https://github.com/intel-lab-lkp/linux git fetch --no-tags linux-review Kees-Cook/kunit-tool-Enable-CONFIG_FORTIFY_SOURCE-under-UML/20230406-081014 git checkout 4fd520e6ee549e1ffe8859e26e57ea64b48e78ea # save the config file mkdir build_dir && cp config build_dir/.config COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm olddefconfig COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=arm SHELL=/bin/bash If you fix the issue, kindly add following tag where applicable | Reported-by: kernel test robot | Link: https://lore.kernel.org/oe-kbuild-all/202304061930.4Au0PASm-lkp@intel.com/ All errors (new ones prefixed by >>): >> ld.lld: error: undefined symbol: __fortify_panic >>> referenced by fortify-string.h:208 (include/linux/fortify-string.h:208) >>> arch/arm/boot/compressed/fdt_ro.o:(fdt_stringlist_count) >>> referenced by fortify-string.h:208 (include/linux/fortify-string.h:208) >>> arch/arm/boot/compressed/fdt_ro.o:(fdt_stringlist_search) >>> referenced by fortify-string.h:208 (include/linux/fortify-string.h:208) >>> arch/arm/boot/compressed/fdt_ro.o:(fdt_stringlist_get) -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests