From: kernel test robot <lkp@intel.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: oe-kbuild-all@lists.linux.dev,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-cxl@vger.kernel.org
Subject: [cxl:for-6.3/cxl-ram-region 16/18] lib/stackinit_kunit.c:34:13: error: conflicting types for 'range_contains'; have 'bool(char *, size_t, char *, size_t)' {aka '_Bool(char *, unsigned int, char *, unsigned int)'}
Date: Sat, 28 Jan 2023 19:52:56 +0800 [thread overview]
Message-ID: <202301281924.bar72HY6-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git for-6.3/cxl-ram-region
head: a7cf664d7e997ac36b0f466af2e2be33464ab598
commit: b879b3c78181c4a89c4a15d6cd7fc75cb1a353a6 [16/18] kernel/range: Uplevel the cxl subsystem's range_contains() helper
config: i386-allyesconfig (https://download.01.org/0day-ci/archive/20230128/202301281924.bar72HY6-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git/commit/?id=b879b3c78181c4a89c4a15d6cd7fc75cb1a353a6
git remote add cxl https://git.kernel.org/pub/scm/linux/kernel/git/cxl/cxl.git
git fetch --no-tags cxl for-6.3/cxl-ram-region
git checkout b879b3c78181c4a89c4a15d6cd7fc75cb1a353a6
# save the config file
mkdir build_dir && cp config build_dir/.config
make W=1 O=build_dir ARCH=i386 olddefconfig
make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> lib/stackinit_kunit.c:34:13: error: conflicting types for 'range_contains'; have 'bool(char *, size_t, char *, size_t)' {aka '_Bool(char *, unsigned int, char *, unsigned int)'}
34 | static bool range_contains(char *haystack_start, size_t haystack_size,
| ^~~~~~~~~~~~~~
In file included from arch/x86/include/asm/page.h:21,
from arch/x86/include/asm/thread_info.h:12,
from include/linux/thread_info.h:60,
from arch/x86/include/asm/preempt.h:9,
from include/linux/preempt.h:78,
from include/linux/spinlock.h:56,
from include/linux/kref.h:16,
from include/kunit/test.h:21,
from lib/stackinit_kunit.c:14:
include/linux/range.h:16:20: note: previous definition of 'range_contains' with type 'bool(struct range *, struct range *)' {aka '_Bool(struct range *, struct range *)'}
16 | static inline bool range_contains(struct range *r1, struct range *r2)
| ^~~~~~~~~~~~~~
vim +34 lib/stackinit_kunit.c
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 33
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 @34 static bool range_contains(char *haystack_start, size_t haystack_size,
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 35 char *needle_start, size_t needle_size)
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 36 {
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 37 if (needle_start >= haystack_start &&
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 38 needle_start + needle_size <= haystack_start + haystack_size)
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 39 return true;
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 40 return false;
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 41 }
50ceaa95ea0970 lib/test_stackinit.c Kees Cook 2019-01-23 42
:::::: The code at line 34 was first introduced by commit
:::::: 50ceaa95ea09703722b30b4afa617c972071cd7f lib: Introduce test_stackinit module
:::::: TO: Kees Cook <keescook@chromium.org>
:::::: CC: Kees Cook <keescook@chromium.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-01-28 11:53 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=202301281924.bar72HY6-lkp@intel.com \
--to=lkp@intel.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vishal.l.verma@intel.com \
/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