From: kernel test robot <lkp@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Kevin Tian <kevin.tian@intel.com>,
Eric Auger <eric.auger@redhat.com>,
Nicolin Chen <nicolinc@nvidia.com>
Subject: drivers/iommu/iommufd/vfio_compat.c:315:17: sparse: sparse: cast removes address space '__user' of expression
Date: Thu, 11 Jan 2024 23:05:36 +0800 [thread overview]
Message-ID: <202401112201.oMA1N8EM-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: de927f6c0b07d9e698416c5b287c521b07694cac
commit: d624d6652a65ad4f47a58b8651a1ec1163bb81d3 iommufd: vfio container FD ioctl compatibility
date: 1 year, 1 month ago
config: arm64-randconfig-r132-20240105 (https://download.01.org/0day-ci/archive/20240111/202401112201.oMA1N8EM-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.2.0
reproduce: (https://download.01.org/0day-ci/archive/20240111/202401112201.oMA1N8EM-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/202401112201.oMA1N8EM-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/iommufd/vfio_compat.c:315:17: sparse: sparse: cast removes address space '__user' of expression
vim +/__user +315 drivers/iommu/iommufd/vfio_compat.c
309
310 static int iommufd_fill_cap_iova(struct iommufd_ioas *ioas,
311 struct vfio_info_cap_header __user *cur,
312 size_t avail)
313 {
314 struct vfio_iommu_type1_info_cap_iova_range __user *ucap_iovas =
> 315 container_of(cur,
316 struct vfio_iommu_type1_info_cap_iova_range __user,
317 header);
318 struct vfio_iommu_type1_info_cap_iova_range cap_iovas = {
319 .header = {
320 .id = VFIO_IOMMU_TYPE1_INFO_CAP_IOVA_RANGE,
321 .version = 1,
322 },
323 };
324 struct interval_tree_span_iter span;
325
326 interval_tree_for_each_span(&span, &ioas->iopt.reserved_itree, 0,
327 ULONG_MAX) {
328 struct vfio_iova_range range;
329
330 if (!span.is_hole)
331 continue;
332 range.start = span.start_hole;
333 range.end = span.last_hole;
334 if (avail >= struct_size(&cap_iovas, iova_ranges,
335 cap_iovas.nr_iovas + 1) &&
336 copy_to_user(&ucap_iovas->iova_ranges[cap_iovas.nr_iovas],
337 &range, sizeof(range)))
338 return -EFAULT;
339 cap_iovas.nr_iovas++;
340 }
341 if (avail >= struct_size(&cap_iovas, iova_ranges, cap_iovas.nr_iovas) &&
342 copy_to_user(ucap_iovas, &cap_iovas, sizeof(cap_iovas)))
343 return -EFAULT;
344 return struct_size(&cap_iovas, iova_ranges, cap_iovas.nr_iovas);
345 }
346
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-01-11 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 15:05 kernel test robot [this message]
2024-01-11 15:40 ` drivers/iommu/iommufd/vfio_compat.c:315:17: sparse: sparse: cast removes address space '__user' of expression Jason Gunthorpe
-- strict thread matches above, loose matches on Subject: below --
2023-09-10 13:16 kernel test robot
2023-09-10 3:25 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=202401112201.oMA1N8EM-lkp@intel.com \
--to=lkp@intel.com \
--cc=eric.auger@redhat.com \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolinc@nvidia.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.