All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "Thomas Weißschuh (Schneider Electric)"
	<thomas.weissschuh@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [thomas-weissschuh:b4/auxclock-nanosleep 17/44] kernel/time/benchmarks.c:112:40: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 30 Apr 2026 11:55:28 +0800	[thread overview]
Message-ID: <202604301131.MSMUGlNW-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/thomas.weissschuh/linux.git b4/auxclock-nanosleep
head:   3e5442acb7e21f08c3eff2ecdace624b6647d5b1
commit: 2d4cde60596e5113f58afbb253423ffcabc891ac [17/44] benchmarks
config: i386-randconfig-r131-20260430 (https://download.01.org/0day-ci/archive/20260430/202604301131.MSMUGlNW-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260430/202604301131.MSMUGlNW-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/202604301131.MSMUGlNW-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> kernel/time/benchmarks.c:112:40: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void [noderef] __user *to @@     got char *buf @@
   kernel/time/benchmarks.c:112:40: sparse:     expected void [noderef] __user *to
   kernel/time/benchmarks.c:112:40: sparse:     got char *buf
>> kernel/time/benchmarks.c:119:20: sparse: sparse: incorrect type in initializer (incompatible argument 2 (different address spaces)) @@     expected int ( *read )( ... ) @@     got int ( * )( ... ) @@
   kernel/time/benchmarks.c:119:20: sparse:     expected int ( *read )( ... )
   kernel/time/benchmarks.c:119:20: sparse:     got int ( * )( ... )

vim +112 kernel/time/benchmarks.c

   107	
   108	static ssize_t benchmark_file_read(struct file *f, char *buf, size_t size, loff_t *ppos)
   109	{
   110		struct benchmark_private *private = f->private_data;
   111	
 > 112		return simple_read_from_buffer(buf, size, ppos, private->samples.d, sizeof(private->samples.d));
   113	}
   114	
   115	static const struct file_operations benchmark_fops = {
   116		.owner	 = THIS_MODULE,
   117		.open	 = benchmark_file_open,
   118		.release = benchmark_file_release,
 > 119		.read	 = benchmark_file_read,
   120	};
   121	

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

                 reply	other threads:[~2026-04-30  3:55 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=202604301131.MSMUGlNW-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=thomas.weissschuh@linutronix.de \
    /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.