From: kernel test robot <lkp@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
intel-xe@lists.freedesktop.org
Cc: oe-kbuild-all@lists.linux.dev,
Michal Wajdeczko <michal.wajdeczko@intel.com>,
Matthew Wilcox <willy@infradead.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Matthew Brost <matthew.brost@intel.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] iov_iter: Provide copy_iomem_to|from_iter()
Date: Thu, 14 Nov 2024 12:20:23 +0800 [thread overview]
Message-ID: <202411141227.4kDiZIXM-lkp@intel.com> (raw)
In-Reply-To: <20241112200454.2211-2-michal.wajdeczko@intel.com>
Hi Michal,
kernel test robot noticed the following build warnings:
[auto build test WARNING on drm-xe/drm-xe-next]
[also build test WARNING on brauner-vfs/vfs.all akpm-mm/mm-nonmm-unstable linus/master v6.12-rc7 next-20241113]
[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/Michal-Wajdeczko/iov_iter-Provide-copy_iomem_to-from_iter/20241113-080831
base: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
patch link: https://lore.kernel.org/r/20241112200454.2211-2-michal.wajdeczko%40intel.com
patch subject: [PATCH v2 1/4] iov_iter: Provide copy_iomem_to|from_iter()
config: arm-randconfig-r113-20241113 (https://download.01.org/0day-ci/archive/20241114/202411141227.4kDiZIXM-lkp@intel.com/config)
compiler: clang version 16.0.6 (https://github.com/llvm/llvm-project 7cbf1a2591520c2491aa35339f227775f4d3adf6)
reproduce: (https://download.01.org/0day-ci/archive/20241114/202411141227.4kDiZIXM-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/202411141227.4kDiZIXM-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
lib/iov_iter.c:373:47: sparse: sparse: cast removes address space '__iomem' of expression
lib/iov_iter.c:386:47: sparse: sparse: cast removes address space '__iomem' of expression
>> lib/iov_iter.c:349:9: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const volatile [noderef] __iomem *from @@ got void * @@
lib/iov_iter.c:349:9: sparse: expected void const volatile [noderef] __iomem *from
lib/iov_iter.c:349:9: sparse: got void *
lib/iov_iter.c:330:9: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const volatile [noderef] __iomem *from @@ got void * @@
lib/iov_iter.c:330:9: sparse: expected void const volatile [noderef] __iomem *from
lib/iov_iter.c:330:9: sparse: got void *
>> lib/iov_iter.c:362:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *to @@ got void *to @@
lib/iov_iter.c:362:9: sparse: expected void volatile [noderef] __iomem *to
lib/iov_iter.c:362:9: sparse: got void *to
>> lib/iov_iter.c:338:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void volatile [noderef] __iomem *to @@ got void * @@
lib/iov_iter.c:338:9: sparse: expected void volatile [noderef] __iomem *to
lib/iov_iter.c:338:9: sparse: got void *
vim +349 lib/iov_iter.c
333
334 static __always_inline
335 size_t memcpy_iomem_from_iter(void *iter_from, size_t progress, size_t len,
336 void *to, void *priv2)
337 {
> 338 memcpy_toio(to + progress, iter_from, len);
339 return 0;
340 }
341
342 static __always_inline
343 size_t copy_iomem_to_user_iter(void __user *iter_to, size_t progress,
344 size_t len, void *from, void *priv2)
345 {
346 unsigned char buf[SMP_CACHE_BYTES];
347 size_t chunk = min(len, sizeof(buf));
348
> 349 memcpy_fromio(buf, from + progress, chunk);
350 chunk -= copy_to_user_iter(iter_to, progress, chunk, buf, priv2);
351 return len - chunk;
352 }
353
354 static __always_inline
355 size_t copy_iomem_from_user_iter(void __user *iter_from, size_t progress,
356 size_t len, void *to, void *priv2)
357 {
358 unsigned char buf[SMP_CACHE_BYTES];
359 size_t chunk = min(len, sizeof(buf));
360
361 chunk -= copy_from_user_iter(iter_from, progress, chunk, buf, priv2);
> 362 memcpy_toio(to, buf, chunk);
363 return len - chunk;
364 }
365
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-14 4:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 20:04 [PATCH v2 0/4] Add iomem helpers for use from debugfs Michal Wajdeczko
2024-11-12 20:04 ` [PATCH v2 1/4] iov_iter: Provide copy_iomem_to|from_iter() Michal Wajdeczko
2024-11-14 1:29 ` kernel test robot
2024-11-14 4:20 ` kernel test robot [this message]
2024-11-14 14:12 ` [PATCH v3 " Michal Wajdeczko
2024-11-12 20:04 ` [PATCH v2 2/4] libfs: Provide simple_read_from|write_to_iomem() Michal Wajdeczko
2024-11-12 20:04 ` [PATCH v2 3/4] drm/xe: Add read/write debugfs helpers for GGTT node Michal Wajdeczko
2024-11-12 20:04 ` [PATCH v2 4/4] drm/xe/pf: Expose access to the VF GGTT PTEs over debugfs Michal Wajdeczko
2024-11-13 10:17 ` ✓ CI.Patch_applied: success for Add iomem helpers for use from debugfs (rev2) Patchwork
2024-11-13 10:17 ` ✓ CI.checkpatch: " Patchwork
2024-11-13 10:18 ` ✓ CI.KUnit: " Patchwork
2024-11-13 10:30 ` ✓ CI.Build: " Patchwork
2024-11-13 10:33 ` ✓ CI.Hooks: " Patchwork
2024-11-13 10:34 ` ✗ CI.checksparse: warning " Patchwork
2024-11-13 10:58 ` ✓ CI.BAT: success " Patchwork
2024-11-13 13:52 ` ✗ CI.FULL: failure " Patchwork
2024-11-14 14:38 ` ✓ CI.Patch_applied: success for Add iomem helpers for use from debugfs (rev3) Patchwork
2024-11-14 14:38 ` ✓ CI.checkpatch: " Patchwork
2024-11-14 14:39 ` ✓ CI.KUnit: " Patchwork
2024-11-14 14:51 ` ✓ CI.Build: " Patchwork
2024-11-14 14:53 ` ✓ CI.Hooks: " Patchwork
2024-11-14 14:54 ` ✗ CI.checksparse: warning " Patchwork
2024-11-14 15:12 ` ✓ CI.BAT: success " Patchwork
2024-11-15 4:55 ` ✗ CI.FULL: failure " Patchwork
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=202411141227.4kDiZIXM-lkp@intel.com \
--to=lkp@intel.com \
--cc=akpm@linux-foundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthew.brost@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
/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.