All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-6.1 9/10] crypto/fips140-module.c:46:11: sparse: sparse: symbol '__initcall_start_marker' was not declared. Should it be static?
Date: Thu, 25 Apr 2024 19:23:14 +0800	[thread overview]
Message-ID: <202404251918.dRQcw18e-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android14-6.1
head:   c61278bb705a1891885b578a71656264da61be5b
commit: c6d5a767217ce93403528e99f1a1eb401a26eeb3 [9/10] ANDROID: fips140: add kernel crypto module
config: arm64-randconfig-r112-20240425 (https://download.01.org/0day-ci/archive/20240425/202404251918.dRQcw18e-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 5ef5eb66fb428aaf61fb51b709f065c069c11242)
reproduce: (https://download.01.org/0day-ci/archive/20240425/202404251918.dRQcw18e-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/202404251918.dRQcw18e-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> crypto/fips140-module.c:46:11: sparse: sparse: symbol '__initcall_start_marker' was not declared. Should it be static?
>> crypto/fips140-module.c:47:11: sparse: sparse: symbol '__initcall_end_marker' was not declared. Should it be static?
>> crypto/fips140-module.c:62:10: sparse: sparse: symbol '__text_start' was not declared. Should it be static?
>> crypto/fips140-module.c:63:10: sparse: sparse: symbol '__rodata_start' was not declared. Should it be static?

vim +/__initcall_start_marker +46 crypto/fips140-module.c

    45	
  > 46	const u32 __initcall_start_marker __section(".initcalls._start");
  > 47	const u32 __initcall_end_marker __section(".initcalls._end");
    48	
    49	const u8 __fips140_text_start __section(".text.._start");
    50	const u8 __fips140_text_end __section(".text.._end");
    51	
    52	const u8 __fips140_rodata_start __section(".rodata.._start");
    53	const u8 __fips140_rodata_end __section(".rodata.._end");
    54	
    55	/*
    56	 * We need this little detour to prevent Clang from detecting out of bounds
    57	 * accesses to __fips140_text_start and __fips140_rodata_start, which only exist
    58	 * to delineate the section, and so their sizes are not relevant to us.
    59	 */
    60	const u32 *__initcall_start = &__initcall_start_marker;
    61	
  > 62	const u8 *__text_start = &__fips140_text_start;
  > 63	const u8 *__rodata_start = &__fips140_rodata_start;
    64	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2024-04-25 11:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 11:23 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-04-25  8:05 [android-common:android14-6.1 9/10] crypto/fips140-module.c:46:11: sparse: sparse: symbol '__initcall_start_marker' was not declared. Should it be static? kernel test robot

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=202404251918.dRQcw18e-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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 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.