From: kernel test robot <lkp@intel.com>
To: Ard Biesheuvel <ardb+git@google.com>, x86@kernel.org
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev,
linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
stable@vger.kernel.org, Fangrui Song <i@maskray.me>,
Brian Gerst <brgerst@gmail.com>, Uros Bizjak <ubizjak@gmail.com>,
Nathan Chancellor <nathan@kernel.org>,
Andy Lutomirski <luto@kernel.org>
Subject: Re: [PATCH] x86/stackprotector: Work around strict Clang TLS symbol requirements
Date: Fri, 4 Oct 2024 01:55:55 +0800 [thread overview]
Message-ID: <202410040122.shftyeMf-lkp@intel.com> (raw)
In-Reply-To: <20241002092534.3163838-2-ardb+git@google.com>
Hi Ard,
kernel test robot noticed the following build warnings:
[auto build test WARNING on tip/x86/core]
[also build test WARNING on tip/master linus/master tip/x86/asm v6.12-rc1 next-20241003]
[cannot apply to tip/auto-latest]
[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/Ard-Biesheuvel/x86-stackprotector-Work-around-strict-Clang-TLS-symbol-requirements/20241002-172733
base: tip/x86/core
patch link: https://lore.kernel.org/r/20241002092534.3163838-2-ardb%2Bgit%40google.com
patch subject: [PATCH] x86/stackprotector: Work around strict Clang TLS symbol requirements
config: i386-randconfig-061-20241003 (https://download.01.org/0day-ci/archive/20241004/202410040122.shftyeMf-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241004/202410040122.shftyeMf-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/202410040122.shftyeMf-lkp@intel.com/
All warnings (new ones prefixed by >>, old ones prefixed by <<):
WARNING: modpost: missing MODULE_DESCRIPTION() in kernel/locking/test-ww_mutex.o
WARNING: modpost: EXPORT symbol "__ref_stack_chk_guard" [vmlinux] version generation failed, symbol will not be versioned.
Is "__ref_stack_chk_guard" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: "__ref_stack_chk_guard" [kernel/rcu/refscale.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [kernel/torture.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [fs/nfs/nfsv4.ko] has no CRC!
>> WARNING: modpost: "__ref_stack_chk_guard" [fs/unicode/utf8-selftest.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [fs/smb/client/cifs.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [crypto/gcm.ko] has no CRC!
>> WARNING: modpost: "__ref_stack_chk_guard" [lib/kunit/kunit-test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/string_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/string_helpers_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/test_hexdump.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/test_hash.ko] has no CRC!
>> WARNING: modpost: "__ref_stack_chk_guard" [lib/test_printf.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/test_scanf.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/test_bitmap.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/test_uuid.ko] has no CRC!
>> WARNING: modpost: "__ref_stack_chk_guard" [lib/cmdline_kunit.ko] has no CRC!
>> WARNING: modpost: "__ref_stack_chk_guard" [lib/memcpy_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/overflow_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/stackinit_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/fortify_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [lib/siphash_kunit.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/gpu/drm/tests/drm_cmdline_parser_test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/gpu/drm/tests/drm_connector_test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/gpu/drm/tests/drm_format_helper_test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/gpu/drm/display/drm_display_helper.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/base/test/property-entry-test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [drivers/power/supply/test_power.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [net/mptcp/mptcp_crypto_test.ko] has no CRC!
WARNING: modpost: "__ref_stack_chk_guard" [net/dns_resolver/dns_resolver.ko] has no CRC!
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-03 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 9:25 [PATCH] x86/stackprotector: Work around strict Clang TLS symbol requirements Ard Biesheuvel
2024-10-02 11:03 ` Ard Biesheuvel
2024-10-05 15:48 ` Brian Gerst
2024-10-09 12:26 ` Ard Biesheuvel
2024-10-03 14:17 ` kernel test robot
2024-10-03 17:55 ` kernel test robot [this message]
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=202410040122.shftyeMf-lkp@intel.com \
--to=lkp@intel.com \
--cc=ardb+git@google.com \
--cc=ardb@kernel.org \
--cc=brgerst@gmail.com \
--cc=i@maskray.me \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=nathan@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=stable@vger.kernel.org \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.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.