From: Baoquan He <bhe@redhat.com>
To: kbuild-all@lists.01.org
Subject: Re: [linux-next:master 7193/9759] arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 07 May 2022 09:28:52 +0800 [thread overview]
Message-ID: <YnXLVA7lhDW3pVg9@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202205062129.oGoY3bdy-lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2554 bytes --]
On 05/06/22 at 09:59pm, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 38a288f5941ef03752887ad86f2d85442358c99a
> commit: 5d8de293c224896a4da99763fce4f9794308caf4 [7193/9759] vmcore: convert copy_oldmem_page() to take an iov_iter
This is an existed warning, not related to the code change in patch
"vmcore: convert copy_oldmem_page() to take an iov_iter". I have queued
a patch to fix the warning, will send it to SuperH maintainer.
> config: sh-randconfig-s032-20220506 (https://download.01.org/0day-ci/archive/20220506/202205062129.oGoY3bdy-lkp(a)intel.com/config)
> compiler: sh4-linux-gcc (GCC) 11.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5d8de293c224896a4da99763fce4f9794308caf4
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 5d8de293c224896a4da99763fce4f9794308caf4
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=sh SHELL=/bin/bash arch/sh/kernel/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
> >> arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *addr @@ got void [noderef] __iomem * @@
> arch/sh/kernel/crash_dump.c:23:36: sparse: expected void const *addr
> arch/sh/kernel/crash_dump.c:23:36: sparse: got void [noderef] __iomem *
>
> vim +23 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 csize = copy_to_iter(vaddr + offset, csize, iter);
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: kernel test robot <lkp@intel.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [linux-next:master 7193/9759] arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sat, 7 May 2022 09:28:52 +0800 [thread overview]
Message-ID: <YnXLVA7lhDW3pVg9@MiWiFi-R3L-srv> (raw)
In-Reply-To: <202205062129.oGoY3bdy-lkp@intel.com>
On 05/06/22 at 09:59pm, kernel test robot wrote:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head: 38a288f5941ef03752887ad86f2d85442358c99a
> commit: 5d8de293c224896a4da99763fce4f9794308caf4 [7193/9759] vmcore: convert copy_oldmem_page() to take an iov_iter
This is an existed warning, not related to the code change in patch
"vmcore: convert copy_oldmem_page() to take an iov_iter". I have queued
a patch to fix the warning, will send it to SuperH maintainer.
> config: sh-randconfig-s032-20220506 (https://download.01.org/0day-ci/archive/20220506/202205062129.oGoY3bdy-lkp@intel.com/config)
> compiler: sh4-linux-gcc (GCC) 11.3.0
> reproduce:
> wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> # apt-get install sparse
> # sparse version: v0.6.4-dirty
> # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=5d8de293c224896a4da99763fce4f9794308caf4
> git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git fetch --no-tags linux-next master
> git checkout 5d8de293c224896a4da99763fce4f9794308caf4
> # save the config file
> mkdir build_dir && cp config build_dir/.config
> COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=sh SHELL=/bin/bash arch/sh/kernel/
>
> If you fix the issue, kindly add following tag as appropriate
> Reported-by: kernel test robot <lkp@intel.com>
>
>
> sparse warnings: (new ones prefixed by >>)
> >> arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const *addr @@ got void [noderef] __iomem * @@
> arch/sh/kernel/crash_dump.c:23:36: sparse: expected void const *addr
> arch/sh/kernel/crash_dump.c:23:36: sparse: got void [noderef] __iomem *
>
> vim +23 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 csize = copy_to_iter(vaddr + offset, csize, iter);
>
> --
> 0-DAY CI Kernel Test Service
> https://01.org/lkp
>
next prev parent reply other threads:[~2022-05-07 1:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 13:59 [linux-next:master 7193/9759] arch/sh/kernel/crash_dump.c:23:36: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2022-05-06 21:31 ` Matthew Wilcox
2022-05-06 21:31 ` Matthew Wilcox
2022-05-07 1:28 ` Baoquan He [this message]
2022-05-07 1:28 ` Baoquan He
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=YnXLVA7lhDW3pVg9@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=kbuild-all@lists.01.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.