All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kaixuxia@tencent.com, frankjpliu@tencent.com, kasong@tencent.com,
	sagazchen@tencent.com, kernelxing@tencent.com,
	aurelianliu@tencent.com, deshengwu@tencent.com,
	flyingpeng@tencent.com, jingqunli@tencent.com,
	jason.zeng@intel.com, wu.zheng@intel.com, yingbao.jia@intel.com,
	pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [opencloudos:next 25/98] net/core/net-procfs.c:344:45: sparse: sparse: cast removes address space '__percpu' of expression
Date: Thu, 31 Oct 2024 03:11:02 +0800	[thread overview]
Message-ID: <202410310318.WeKIPsO0-lkp@intel.com> (raw)

tree:   https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git next
head:   ce9f9d823a41831d622fa11e29c3d620c044f51b
commit: d9324ddd538a0b57dbee8623806ff9b9f7811202 [25/98] net: dev ipv4/v6 stat
config: x86_64-randconfig-122-20241029 (https://download.01.org/0day-ci/archive/20241031/202410310318.WeKIPsO0-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241031/202410310318.WeKIPsO0-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/202410310318.WeKIPsO0-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> net/core/net-procfs.c:344:45: sparse: sparse: cast removes address space '__percpu' of expression
>> net/core/net-procfs.c:344:45: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __percpu *mib @@     got void [noderef] __percpu ** @@
   net/core/net-procfs.c:344:45: sparse:     expected void [noderef] __percpu *mib
   net/core/net-procfs.c:344:45: sparse:     got void [noderef] __percpu **

vim +/__percpu +344 net/core/net-procfs.c

   334	
   335	static void dev_ext_seq_printf_stats(struct seq_file *seq, void *v)
   336	{
   337		struct net_device *dev = (struct net_device *)v;
   338		int i;
   339	
   340		seq_printf(seq, "%10s  ", dev->name);
   341	
   342		for (i = 0; snmp_devstat_list[i].name; i++)
   343			seq_printf(seq, " %12lu",
 > 344				   snmp_fold_field((void __percpu **)
   345						   dev->mib.dev_statistics,
   346						   snmp_devstat_list[i].entry));
   347		seq_putc(seq, '\n');
   348	}
   349	

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

             reply	other threads:[~2024-10-30 19:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-30 19:11 kernel test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-29  8:31 [opencloudos:next 25/98] net/core/net-procfs.c:344:45: sparse: sparse: cast removes address space '__percpu' of expression kernel test robot
2024-03-05  0:01 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=202410310318.WeKIPsO0-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=aurelianliu@tencent.com \
    --cc=deshengwu@tencent.com \
    --cc=flyingpeng@tencent.com \
    --cc=frankjpliu@tencent.com \
    --cc=jason.zeng@intel.com \
    --cc=jingqunli@tencent.com \
    --cc=kaixuxia@tencent.com \
    --cc=kasong@tencent.com \
    --cc=kernelxing@tencent.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pei.p.jia@intel.com \
    --cc=sagazchen@tencent.com \
    --cc=wu.zheng@intel.com \
    --cc=yingbao.jia@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 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.