linux-kernel - Re: drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type in argument 1 (different address spaces)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 09 Nov 2022 08:33:30 +0100
From:   "Arnd Bergmann" <arnd@...db.de>
To:     "kernel test robot" <lkp@...el.com>,
        "Kefeng Wang" <wangkefeng.wang@...wei.com>
Cc:     oe-kbuild-all@...ts.linux.dev, linux-kernel@...r.kernel.org,
        "Will Deacon" <will@...nel.org>, "Christoph Hellwig" <hch@....de>,
        "Russell King" <rmk+kernel@...linux.org.uk>
Subject: Re: drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type
 in argument 1 (different address spaces)

On Wed, Nov 9, 2022, at 04:54, kernel test robot wrote:
> tree:   
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 
> master
> head:   f141df371335645ce29a87d9683a3f79fba7fd67
> commit: d803336abdbc1bfacdb32b2cf9f4fdbee072b8ee ARM: mm: kill unused 
> runtime hook arch_iounmap()

Thanks for the report, but I think it might be better to stop
reporting address space violations from this patch, because it
only started showing existing known issues with a slightly
different error message, or flagging issues on arm32 that
were previously shown on other architectures.

> sparse warnings: (new ones prefixed by >>)
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse: sparse: incorrect 
> type in assignment (different address spaces) @@     expected void *va 
> @@     got void [noderef] __iomem * @@
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse:     expected void 
> *va
>    drivers/remoteproc/st_remoteproc.c:98:12: sparse:     got void 
> [noderef] __iomem *
>>> drivers/remoteproc/st_remoteproc.c:114:20: sparse: sparse: incorrect type in argument 1 (different address spaces) @@     expected void volatile [noderef] __iomem *io_addr @@     got void *va @@

      Arnd