From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:iov-cleanup 14/20] lib/iov_iter.c:208:39: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 21 Sep 2023 22:41:51 +0800 [thread overview]
Message-ID: <202309212239.6vsGPmxF-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git iov-cleanup
head: 1293922ed84ec546e199761c4f570d92c21114ea
commit: 587a6a805e2ebf90427af4f9ac35496678d49ca3 [14/20] iov_iter: Convert iterate*() to inline funcs
config: x86_64-randconfig-121-20230921 (https://download.01.org/0day-ci/archive/20230921/202309212239.6vsGPmxF-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/20230921/202309212239.6vsGPmxF-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/202309212239.6vsGPmxF-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/iov_iter.c:208:39: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void *to @@ got void [noderef] __user *iter_to @@
lib/iov_iter.c:208:39: sparse: expected void *to
lib/iov_iter.c:208:39: sparse: got void [noderef] __user *iter_to
lib/iov_iter.c: note: in included file (through arch/x86/include/asm/uaccess.h, include/linux/uaccess.h, include/linux/sched/task.h, ...):
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
arch/x86/include/asm/uaccess_64.h:88:24: sparse: sparse: cast removes address space '__user' of expression
vim +208 lib/iov_iter.c
199
200 #ifdef CONFIG_ARCH_HAS_COPY_MC
201 static __always_inline
202 size_t copy_to_user_iter_mc(void __user *iter_to, size_t progress,
203 size_t len, void *from, void *priv2)
204 {
205 if (access_ok(iter_to, len)) {
206 from += progress;
207 instrument_copy_to_user(iter_to, from, len);
> 208 len = copy_mc_to_user(iter_to, from, len);
209 }
210 return len;
211 }
212
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-09-21 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 14:41 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-22 1:35 [dhowells-fs:iov-cleanup 14/20] lib/iov_iter.c:208:39: sparse: sparse: incorrect type in argument 1 (different address spaces) 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=202309212239.6vsGPmxF-lkp@intel.com \
--to=lkp@intel.com \
--cc=dhowells@redhat.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.