From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
David Gow <davidgow@google.com>
Subject: lib/fortify_kunit.c:28:9: sparse: sparse: incompatible types for operation (==):
Date: Sun, 19 Mar 2023 12:40:21 +0800 [thread overview]
Message-ID: <202303191230.4hAT1iek-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: a3671bd86a9770e34969522d29bb30a1b66fd88a
commit: 875bfd5276f31d09e811d31fca638b9f4d1205e8 fortify: Add KUnit test for FORTIFY_SOURCE internals
date: 6 months ago
config: s390-randconfig-s032-20230319 (https://download.01.org/0day-ci/archive/20230319/202303191230.4hAT1iek-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 12.1.0
reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version: v0.6.4-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=875bfd5276f31d09e811d31fca638b9f4d1205e8
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout 875bfd5276f31d09e811d31fca638b9f4d1205e8
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=s390 olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=s390 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303191230.4hAT1iek-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
lib/fortify_kunit.c:28:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:28:9: sparse: sparse: undefined identifier '__compiletime_strlen'
>> lib/fortify_kunit.c:28:9: sparse: sparse: incompatible types for operation (==):
>> lib/fortify_kunit.c:28:9: sparse: bad type const __left
>> lib/fortify_kunit.c:28:9: sparse: int const __right
lib/fortify_kunit.c:29:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:29:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:29:9: sparse: sparse: incompatible types for operation (==):
lib/fortify_kunit.c:29:9: sparse: bad type const __left
lib/fortify_kunit.c:29:9: sparse: int const __right
lib/fortify_kunit.c:30:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:30:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:30:9: sparse: sparse: incompatible types for operation (==):
lib/fortify_kunit.c:30:9: sparse: bad type const __left
lib/fortify_kunit.c:30:9: sparse: int const __right
lib/fortify_kunit.c:32:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:32:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:32:9: sparse: sparse: incompatible types for operation (==):
lib/fortify_kunit.c:32:9: sparse: bad type const __left
>> lib/fortify_kunit.c:32:9: sparse: unsigned long const __right
lib/fortify_kunit.c:34:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:34:9: sparse: sparse: undefined identifier '__compiletime_strlen'
lib/fortify_kunit.c:34:9: sparse: sparse: incompatible types for operation (==):
lib/fortify_kunit.c:34:9: sparse: bad type const __left
lib/fortify_kunit.c:34:9: sparse: unsigned long const __right
lib/fortify_kunit.c:56:16: sparse: sparse: undefined identifier '__compiletime_strlen'
vim +28 lib/fortify_kunit.c
25
26 static void known_sizes_test(struct kunit *test)
27 {
> 28 KUNIT_EXPECT_EQ(test, __compiletime_strlen("88888888"), 8);
29 KUNIT_EXPECT_EQ(test, __compiletime_strlen(array_of_10), 10);
> 30 KUNIT_EXPECT_EQ(test, __compiletime_strlen(ptr_of_11), 11);
31
> 32 KUNIT_EXPECT_EQ(test, __compiletime_strlen(array_unknown), SIZE_MAX);
33 /* Externally defined and dynamically sized string pointer: */
34 KUNIT_EXPECT_EQ(test, __compiletime_strlen(saved_command_line), SIZE_MAX);
35 }
36
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
next reply other threads:[~2023-03-19 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-19 4:40 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-23 13:09 lib/fortify_kunit.c:28:9: sparse: sparse: incompatible types for operation (==): kernel test robot
2023-02-06 17:14 kernel test robot
2022-11-18 14:09 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=202303191230.4hAT1iek-lkp@intel.com \
--to=lkp@intel.com \
--cc=davidgow@google.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).