linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Alexander Lobakin <aleksander.lobakin@intel.com>
Subject: [linux-next:master 8181/9122] lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
Date: Thu, 22 Feb 2024 22:47:20 +0800	[thread overview]
Message-ID: <202402222223.h9rFmYj4-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   e31185ce00a96232308300008db193416ceb9769
commit: 0f4459080884b688c4ec9c2b121f22c641401bc1 [8181/9122] fortify: Split reporting and avoid passing string pointer
config: s390-randconfig-r123-20240222 (https://download.01.org/0day-ci/archive/20240222/202402222223.h9rFmYj4-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240222/202402222223.h9rFmYj4-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/202402222223.h9rFmYj4-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: cast from unknown type
   lib/string_helpers.c:1023:34: sparse: sparse: cast from unknown type
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types in conditional expression (different types):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    int *
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: bad constant expression type
   lib/string_helpers.c:1013:9: sparse: sparse: undefined identifier 'EACH_FORTIFY_FUNC'
   lib/string_helpers.c:1019:25: sparse: sparse: undefined identifier 'FORTIFY_REASON_FUNC'
   lib/string_helpers.c:1020:28: sparse: sparse: undefined identifier 'FORTIFY_REASON_DIR'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: cast from unknown type
   lib/string_helpers.c:1023:34: sparse: sparse: cast from unknown type
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types in conditional expression (different types):
   lib/string_helpers.c:1023:34: sparse:    bad type
   lib/string_helpers.c:1023:34: sparse:    int *
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
   lib/string_helpers.c:1023:34: sparse: sparse: undefined identifier 'FORTIFY_FUNC_UNKNOWN'
>> lib/string_helpers.c:1023:34: sparse: sparse: incompatible types for operation (<):
   lib/string_helpers.c:1023:34: sparse:    unsigned long long __UNIQUE_ID___x302
   lib/string_helpers.c:1023:34: sparse:    bad type __UNIQUE_ID___y303

vim +1023 lib/string_helpers.c

  1016	
  1017	void __fortify_report(const u8 reason)
  1018	{
  1019		const u8 func = FORTIFY_REASON_FUNC(reason);
  1020		const bool write = FORTIFY_REASON_DIR(reason);
  1021		const char *name;
  1022	
> 1023		name = fortify_func_name[umin(func, FORTIFY_FUNC_UNKNOWN)];
  1024		WARN(1, "%s: detected buffer %s overflow\n", name, str_read_write(!write));
  1025	}
  1026	EXPORT_SYMBOL(__fortify_report);
  1027	

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


                 reply	other threads:[~2024-02-22 14:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202402222223.h9rFmYj4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aleksander.lobakin@intel.com \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.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