From: kernel test robot <lkp@intel.com>
To: Juergen Gross <jgross@suse.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: [linux-next:master 12386/12880] arch/x86/xen/multicalls.c:59:10: sparse: sparse: incorrect type in initializer (different address spaces)
Date: Mon, 15 Jul 2024 11:51:25 +0800 [thread overview]
Message-ID: <202407151106.5s7Mnfpz-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 3fe121b622825ff8cc995a1e6b026181c48188db
commit: 942d917cb92af2277db9e3be0d62345d770d5996 [12386/12880] xen: make multicall debug boot time selectable
config: x86_64-randconfig-123-20240715 (https://download.01.org/0day-ci/archive/20240715/202407151106.5s7Mnfpz-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240715/202407151106.5s7Mnfpz-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/202407151106.5s7Mnfpz-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/x86/xen/multicalls.c:59:10: sparse: sparse: incorrect type in initializer (different address spaces) @@ expected struct mc_debug_data [noderef] __percpu *static [toplevel] mc_debug_data @@ got struct mc_debug_data * @@
arch/x86/xen/multicalls.c:59:10: sparse: expected struct mc_debug_data [noderef] __percpu *static [toplevel] mc_debug_data
arch/x86/xen/multicalls.c:59:10: sparse: got struct mc_debug_data *
arch/x86/xen/multicalls.c: note: in included file (through include/linux/mmzone.h, include/linux/gfp.h, include/linux/xarray.h, ...):
include/linux/page-flags.h:240:46: sparse: sparse: self-comparison always evaluates to false
include/linux/page-flags.h:240:46: sparse: sparse: self-comparison always evaluates to false
vim +59 arch/x86/xen/multicalls.c
55
56 static DEFINE_PER_CPU(struct mc_buffer, mc_buffer);
57 static struct mc_debug_data mc_debug_data_early __initdata;
58 static struct mc_debug_data __percpu *mc_debug_data __refdata =
> 59 &mc_debug_data_early;
60 DEFINE_PER_CPU(unsigned long, xen_mc_irq_flags);
61
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-07-15 3: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=202407151106.5s7Mnfpz-lkp@intel.com \
--to=lkp@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--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