From: kernel test robot <lkp@intel.com>
To: David Howells <dhowells@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [dhowells-fs:ceph-iter 1/18] lib/iov_iter.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Mon, 7 Aug 2023 13:32:23 +0800 [thread overview]
Message-ID: <202308071349.NFP7QACA-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git ceph-iter
head: 672499b5bfaeda1769d9eab9c9a08f4c2b2e4bf5
commit: f008e454544ebdcf3742c4d4e3d06abe5868be00 [1/18] iov_iter: Add function to see if buffer is all zeros
config: powerpc-randconfig-r081-20230807 (https://download.01.org/0day-ci/archive/20230807/202308071349.NFP7QACA-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 12.3.0
reproduce: (https://download.01.org/0day-ci/archive/20230807/202308071349.NFP7QACA-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/202308071349.NFP7QACA-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> lib/iov_iter.c:582:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *s @@ got void [noderef] __user *[assigned] base @@
lib/iov_iter.c:582:9: sparse: expected void const *s
lib/iov_iter.c:582:9: sparse: got void [noderef] __user *[assigned] base
>> lib/iov_iter.c:582:9: sparse: sparse: subtraction of different types can't work (different address spaces)
>> lib/iov_iter.c:582:9: sparse: sparse: subtraction of different types can't work (different address spaces)
vim +582 lib/iov_iter.c
568
569 /**
570 * iov_iter_is_zero - Return true if the buffer is entirely zeroed
571 * @i: The iterator describing the buffer
572 * @count: Amount of buffer to scan
573 *
574 * Scans the specified amount of the supplied buffer and returns true if only
575 * zero bytes are found therein and false otherwise.
576 */
577 bool iov_iter_is_zero(const struct iov_iter *i, size_t count)
578 {
579 struct iov_iter j = *i, *pj = &j;
580 void *p;
581
> 582 iterate_and_advance(pj, count, base, len, count,
583 ({ p = memchr_inv(base, 0, len); p ? p - base : len; }),
584 ({ p = memchr_inv(base, 0, len); p ? p - base : len; })
585 )
586
587 return !count;
588 }
589 EXPORT_SYMBOL(iov_iter_is_zero);
590
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2023-08-07 5:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 5:32 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-08 7:21 [dhowells-fs:ceph-iter 1/18] lib/iov_iter.c:582:9: 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=202308071349.NFP7QACA-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.