From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-desktop 24/24] arch/arm64/kvm/../../../virt/kvm/vfio.c:400:45: sparse: sparse: incorrect type in argument 2 (different address spaces)
Date: Thu, 28 Aug 2025 00:18:12 +0800 [thread overview]
Message-ID: <202508280010.L6xE5UXP-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android16-6.12-desktop
head: e618ac331b0929e7221e5aadc18783b4b8bc5e2e
commit: b0fccd926d2ee040ec590ca6439db237edf5c247 [24/24] ANDROID: kvm/vfio: pviommu: Add set config IOCTL
config: arm64-randconfig-r122-20250827 (https://download.01.org/0day-ci/archive/20250828/202508280010.L6xE5UXP-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project d26ea02060b1c9db751d188b2edb0059a9eb273d)
reproduce: (https://download.01.org/0day-ci/archive/20250828/202508280010.L6xE5UXP-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/202508280010.L6xE5UXP-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/arm64/kvm/../../../virt/kvm/vfio.c:400:45: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const [noderef] __user *from @@ got void * @@
arch/arm64/kvm/../../../virt/kvm/vfio.c:400:45: sparse: expected void const [noderef] __user *from
arch/arm64/kvm/../../../virt/kvm/vfio.c:400:45: sparse: got void *
>> arch/arm64/kvm/../../../virt/kvm/vfio.c:404:69: sparse: sparse: incorrect type in argument 3 (different address spaces) @@ expected void const [noderef] __user *src @@ got void * @@
arch/arm64/kvm/../../../virt/kvm/vfio.c:404:69: sparse: expected void const [noderef] __user *src
arch/arm64/kvm/../../../virt/kvm/vfio.c:404:69: sparse: got void *
vim +400 arch/arm64/kvm/../../../virt/kvm/vfio.c
391
392 static long pviommufd_ioctl(struct file *filp, unsigned int ioctl,
393 unsigned long arg)
394 {
395 struct kvm_vfio_iommu_config config;
396 __u32 usize;
397
398 switch (ioctl) {
399 case KVM_PVIOMMU_SET_CONFIG:
> 400 if (copy_from_user(&usize, (void *)arg, sizeof(usize)))
401 return -EFAULT;
402 if (usize < offsetofend(struct kvm_vfio_iommu_config, __reserved))
403 return -EINVAL;
> 404 if (copy_struct_from_user(&config, sizeof(config), (void *)arg, usize))
405 return -EFAULT;
406
407 return kvm_vfio_pviommu_set_config(filp, &config);
408 default:
409 return -ENXIO;
410 }
411 return 0;
412 }
413
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-08-27 16:20 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=202508280010.L6xE5UXP-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.