From: kernel test robot <lkp@intel.com>
To: Pavel Begunkov <asml.silence@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [isilence:zctx/devmem 14/15] io_uring/rsrc.c:1227:36: sparse: sparse: incorrect type in argument 3 (different address spaces)
Date: Wed, 08 Jul 2026 09:12:22 +0800 [thread overview]
Message-ID: <202607080831.vyhUT1Ca-lkp@intel.com> (raw)
tree: https://github.com/isilence/linux zctx/devmem
head: ad3d2185448cf828c65336fa4b71233098473a4a
commit: cd188445aee6477a09e0908f090106517becc7c0 [14/15] io_uring/rsrc: add zcrx backed registered buffers
config: arc-randconfig-r122-20260708 (https://download.01.org/0day-ci/archive/20260708/202607080831.vyhUT1Ca-lkp@intel.com/config)
compiler: arc-linux-gcc (GCC) 8.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260708/202607080831.vyhUT1Ca-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/202607080831.vyhUT1Ca-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> io_uring/rsrc.c:1227:36: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void [noderef] __user *buf @@ got void * @@
io_uring/rsrc.c:1227:36: sparse: expected void [noderef] __user *buf
io_uring/rsrc.c:1227:36: sparse: got void *
io_uring/rsrc.c: note: in included file:
io_uring/filetable.h:55:35: sparse: sparse: restricted io_req_flags_t degrades to integer
io_uring/filetable.h:55:35: sparse: sparse: restricted io_req_flags_t degrades to integer
vim +1227 io_uring/rsrc.c
1222
1223 static int io_import_from_zcrx(int ddir, struct iov_iter *iter,
1224 struct io_mapped_ubuf *imu,
1225 u64 buf_addr, size_t len)
1226 {
> 1227 iov_iter_ubuf(iter, ddir, (void *)(unsigned long)buf_addr, len);
1228 return 0;
1229 }
1230
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-07-08 1:13 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=202607080831.vyhUT1Ca-lkp@intel.com \
--to=lkp@intel.com \
--cc=asml.silence@gmail.com \
--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 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.