linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Richard Zhu <hongxing.zhu@nxp.com>,
	Mathieu Poirier <mathieu.poirer@linaro.org>
Subject: [linux-next:master 2434/15421] drivers/remoteproc/imx_rproc.c:315:20: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Thu, 29 Apr 2021 22:28:14 +0800	[thread overview]
Message-ID: <202104292208.UfvwQ41l-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3034 bytes --]

Hi Peng,

First bad commit (maybe != root cause):

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   9e5cff2a1315fec1da1f497714395670366506b6
commit: 2df7062002d0263bde70b453f671bb4f8493e169 [2434/15421] remoteproc: imx_proc: enable virtio/mailbox
config: arm-randconfig-s032-20210429 (attached as .config)
compiler: arm-linux-gnueabi-gcc (GCC) 9.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.3-341-g8af24329-dirty
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=2df7062002d0263bde70b453f671bb4f8493e169
        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 2df7062002d0263bde70b453f671bb4f8493e169
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' W=1 ARCH=arm 

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 >>)
   drivers/remoteproc/imx_rproc.c:298:12: sparse: sparse: incorrect type in assignment (different address spaces) @@     expected void *va @@     got void [noderef] __iomem * @@
   drivers/remoteproc/imx_rproc.c:298:12: sparse:     expected void *va
   drivers/remoteproc/imx_rproc.c:298:12: sparse:     got void [noderef] __iomem *
>> drivers/remoteproc/imx_rproc.c:315:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *iomem_cookie @@     got void *va @@
   drivers/remoteproc/imx_rproc.c:315:20: sparse:     expected void volatile [noderef] __iomem *iomem_cookie
   drivers/remoteproc/imx_rproc.c:315:20: sparse:     got void *va

vim +315 drivers/remoteproc/imx_rproc.c

b29b4249f8f0ca Peng Fan 2021-03-06  310  
b29b4249f8f0ca Peng Fan 2021-03-06  311  static int imx_rproc_mem_release(struct rproc *rproc,
b29b4249f8f0ca Peng Fan 2021-03-06  312  				 struct rproc_mem_entry *mem)
b29b4249f8f0ca Peng Fan 2021-03-06  313  {
b29b4249f8f0ca Peng Fan 2021-03-06  314  	dev_dbg(rproc->dev.parent, "unmap memory: %pa\n", &mem->dma);
b29b4249f8f0ca Peng Fan 2021-03-06 @315  	iounmap(mem->va);
b29b4249f8f0ca Peng Fan 2021-03-06  316  
b29b4249f8f0ca Peng Fan 2021-03-06  317  	return 0;
b29b4249f8f0ca Peng Fan 2021-03-06  318  }
b29b4249f8f0ca Peng Fan 2021-03-06  319  

:::::: The code at line 315 was first introduced by commit
:::::: b29b4249f8f0cad1a1787cbe59e638ff23d489ed remoteproc: imx_rproc: add i.MX specific parse fw hook

:::::: TO: Peng Fan <peng.fan@nxp.com>
:::::: CC: Bjorn Andersson <bjorn.andersson@linaro.org>

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32485 bytes --]

                 reply	other threads:[~2021-04-29 14:28 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=202104292208.UfvwQ41l-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=hongxing.zhu@nxp.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=mathieu.poirer@linaro.org \
    --cc=peng.fan@nxp.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox