Re: [PATCH 2/2] io_uring: introduce IORING_OP_MMAP

[kernel test robot <lkp@intel.com>]

Hi Gabriel,

kernel test robot noticed the following build warnings:

[auto build test WARNING on v6.19-rc7]
[also build test WARNING on linus/master]
[cannot apply to axboe/for-next next-20260129]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Gabriel-Krisman-Bertazi/io_uring-Support-commands-with-optional-file-descriptors/20260130-061445
base:   v6.19-rc7
patch link:    https://lore.kernel.org/r/20260129221138.897715-3-krisman%40suse.de
patch subject: [PATCH 2/2] io_uring: introduce IORING_OP_MMAP
config: m68k-randconfig-r122-20260130 (https://download.01.org/0day-ci/archive/20260130/202601301341.PTetVieu-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260130/202601301341.PTetVieu-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/202601301341.PTetVieu-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> io_uring/mmap.c:116:36: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected void [noderef] __user *addr @@     got void * @@
   io_uring/mmap.c:116:36: sparse:     expected void [noderef] __user *addr
   io_uring/mmap.c:116:36: sparse:     got void *
   io_uring/mmap.c:125:44: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected void [noderef] __user *addr @@     got void * @@
   io_uring/mmap.c:125:44: sparse:     expected void [noderef] __user *addr
   io_uring/mmap.c:125:44: sparse:     got void *
   io_uring/mmap.c:130:28: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected void [noderef] __user *addr @@     got void * @@
   io_uring/mmap.c:130:28: sparse:     expected void [noderef] __user *addr
   io_uring/mmap.c:130:28: sparse:     got void *

vim +116 io_uring/mmap.c

    83	
    84	int io_mmap(struct io_kiocb *req, unsigned int issue_flags)
    85	{
    86		struct io_mmap_data *mmap = io_kiocb_to_cmd(req, struct io_mmap_data);
    87		struct io_mmap_async *data = (struct io_mmap_async *) req->async_data;
    88		int i, mapped, ret;
    89	
    90		if (unlikely(mmap->flags & MAP_HUGETLB && req->file &&
    91			     !is_file_hugepages(req->file))) {
    92			ret = -EINVAL;
    93			goto out;
    94		}
    95	
    96		for (i = 0; i < data->nr_maps; i++) {
    97			struct io_uring_mmap_desc *desc = &data->maps[i];
    98	
    99			if (copy_from_user(desc, &mmap->uaddr[i], sizeof(*desc))) {
   100				ret = -EFAULT;
   101				goto out;
   102			}
   103		}
   104	
   105		mapped = 0;
   106		while (mapped < data->nr_maps) {
   107			struct io_uring_mmap_desc *desc = &data->maps[mapped++];
   108			unsigned long flags = (mmap->flags | desc->flags);
   109			unsigned long len = desc->len;
   110			struct file *file = req->file;
   111	
   112			/* These cannot be mixed and matched.  need to be passed
   113			 * on the SQE.
   114			 */
   115			if (unlikely(desc->flags & (MAP_ANONYMOUS|MAP_HUGETLB))) {
 > 116				desc->addr = ERR_PTR(-EINVAL);

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