From: kernel test robot <lkp@intel.com>
To: Christian Brauner <brauner@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Alexander Mikhalitsyn <alex@amutable.com>
Subject: [linux-next:master 6831/9180] arch/sh/kernel/crash_dump.c:26:43: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 19 Nov 2026 09:06:33 +0100 [thread overview]
Message-ID: <20261119085855.FAscxfBS-lkp@intel.com> (raw)
Hi Christian,
FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: e8017d29067fd1310a65c3494ce1a1b492adbac6
commit: e69501a923a5f2c6995a57a1f2ef9c723b66a78c [6831/9180] crash_dump: use copy_oldmem_to_iter() everywhere
config: sh-randconfig-r2304-20261119 (https://download.01.org/0day-ci/archive/20261119/20261119085855.FAscxfBS-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 12.5.0
sparse: v0.6.5-rc1-21-g84ec0658
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261119/20261119085855.FAscxfBS-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/20261119085855.FAscxfBS-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> arch/sh/kernel/crash_dump.c:26:43: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *src @@ got void [noderef] __iomem * @@
arch/sh/kernel/crash_dump.c:26:43: sparse: expected void const *src
arch/sh/kernel/crash_dump.c:26:43: sparse: got void [noderef] __iomem *
vim +26 arch/sh/kernel/crash_dump.c
13
14 ssize_t copy_oldmem_page(struct iov_iter *iter, unsigned long pfn,
15 size_t csize, unsigned long offset)
16 {
17 void __iomem *vaddr;
18
19 if (!csize)
20 return 0;
21
22 vaddr = ioremap(pfn << PAGE_SHIFT, PAGE_SIZE);
23 if (!vaddr)
24 return -ENOMEM;
25
> 26 csize = copy_oldmem_to_iter(vaddr + offset, csize, iter);
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-19 8:07 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=20261119085855.FAscxfBS-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex@amutable.com \
--cc=brauner@kernel.org \
--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.