From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: drivers/firmware/meson/meson_sm.c:206:9: sparse: sparse: incorrect type in argument 1 (different address spaces)
Date: Sun, 17 Jul 2022 05:17:24 +0800 [thread overview]
Message-ID: <202207170508.3M7C3ier-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: c5fe7a97f20c7f3070ac870144515c0fabc6b999
commit: f68f2ff91512c199ec24883001245912afc17873 fortify: Detect struct member overflows in memcpy() at compile-time
date: 5 months ago
config: arm64-randconfig-s031-20220717 (https://download.01.org/0day-ci/archive/20220717/202207170508.3M7C3ier-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 12.1.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-39-gce1a6720-dirty
# https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f68f2ff91512c199ec24883001245912afc17873
git remote add linus https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
git fetch --no-tags linus master
git checkout f68f2ff91512c199ec24883001245912afc17873
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-12.1.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=arm64 SHELL=/bin/bash drivers/firmware/meson/ drivers/mtd/nand/raw/
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
sparse warnings: (new ones prefixed by >>)
drivers/firmware/meson/meson_sm.c:85:24: sparse: sparse: Using plain integer as NULL pointer
drivers/firmware/meson/meson_sm.c:170:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const * @@ got void [noderef] __iomem *sm_shmem_out_base @@
drivers/firmware/meson/meson_sm.c:170:17: sparse: expected void const *
drivers/firmware/meson/meson_sm.c:170:17: sparse: got void [noderef] __iomem *sm_shmem_out_base
drivers/firmware/meson/meson_sm.c:170:17: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const * @@ got void [noderef] __iomem *sm_shmem_out_base @@
drivers/firmware/meson/meson_sm.c:170:17: sparse: expected void const *
drivers/firmware/meson/meson_sm.c:170:17: sparse: got void [noderef] __iomem *sm_shmem_out_base
drivers/firmware/meson/meson_sm.c:170:17: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const * @@ got void [noderef] __iomem *sm_shmem_out_base @@
drivers/firmware/meson/meson_sm.c:170:17: sparse: expected void const *
drivers/firmware/meson/meson_sm.c:170:17: sparse: got void [noderef] __iomem *sm_shmem_out_base
>> drivers/firmware/meson/meson_sm.c:206:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const * @@ got void [noderef] __iomem *sm_shmem_in_base @@
drivers/firmware/meson/meson_sm.c:206:9: sparse: expected void const *
drivers/firmware/meson/meson_sm.c:206:9: sparse: got void [noderef] __iomem *sm_shmem_in_base
>> drivers/firmware/meson/meson_sm.c:206:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void const * @@ got void [noderef] __iomem *sm_shmem_in_base @@
drivers/firmware/meson/meson_sm.c:206:9: sparse: expected void const *
drivers/firmware/meson/meson_sm.c:206:9: sparse: got void [noderef] __iomem *sm_shmem_in_base
drivers/firmware/meson/meson_sm.c:206:9: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void * @@ got void [noderef] __iomem *sm_shmem_in_base @@
drivers/firmware/meson/meson_sm.c:206:9: sparse: expected void *
drivers/firmware/meson/meson_sm.c:206:9: sparse: got void [noderef] __iomem *sm_shmem_in_base
vim +206 drivers/firmware/meson/meson_sm.c
2c4ddb215521d5 Carlo Caione 2016-08-27 175
2c4ddb215521d5 Carlo Caione 2016-08-27 176 /**
2c4ddb215521d5 Carlo Caione 2016-08-27 177 * meson_sm_call_write - send data to secure-monitor
2c4ddb215521d5 Carlo Caione 2016-08-27 178 *
8cde3c2153e8f5 Carlo Caione 2019-07-31 179 * @fw: Pointer to secure-monitor firmware
2c4ddb215521d5 Carlo Caione 2016-08-27 180 * @buffer: Buffer containing data to send
2c4ddb215521d5 Carlo Caione 2016-08-27 181 * @size: Size of the data to send
2c4ddb215521d5 Carlo Caione 2016-08-27 182 * @cmd_index: Index of the SMC32 function ID
2c4ddb215521d5 Carlo Caione 2016-08-27 183 * @arg0: SMC32 Argument 0
2c4ddb215521d5 Carlo Caione 2016-08-27 184 * @arg1: SMC32 Argument 1
2c4ddb215521d5 Carlo Caione 2016-08-27 185 * @arg2: SMC32 Argument 2
2c4ddb215521d5 Carlo Caione 2016-08-27 186 * @arg3: SMC32 Argument 3
2c4ddb215521d5 Carlo Caione 2016-08-27 187 * @arg4: SMC32 Argument 4
2c4ddb215521d5 Carlo Caione 2016-08-27 188 *
2c4ddb215521d5 Carlo Caione 2016-08-27 189 * Return: size of sent data on success, a negative value on error
2c4ddb215521d5 Carlo Caione 2016-08-27 190 */
8cde3c2153e8f5 Carlo Caione 2019-07-31 191 int meson_sm_call_write(struct meson_sm_firmware *fw, void *buffer,
8cde3c2153e8f5 Carlo Caione 2019-07-31 192 unsigned int size, unsigned int cmd_index, u32 arg0,
8cde3c2153e8f5 Carlo Caione 2019-07-31 193 u32 arg1, u32 arg2, u32 arg3, u32 arg4)
2c4ddb215521d5 Carlo Caione 2016-08-27 194 {
2c4ddb215521d5 Carlo Caione 2016-08-27 195 u32 written;
2c4ddb215521d5 Carlo Caione 2016-08-27 196
8cde3c2153e8f5 Carlo Caione 2019-07-31 197 if (!fw->chip)
2c4ddb215521d5 Carlo Caione 2016-08-27 198 return -ENOENT;
2c4ddb215521d5 Carlo Caione 2016-08-27 199
8cde3c2153e8f5 Carlo Caione 2019-07-31 200 if (size > fw->chip->shmem_size)
2c4ddb215521d5 Carlo Caione 2016-08-27 201 return -EINVAL;
2c4ddb215521d5 Carlo Caione 2016-08-27 202
8cde3c2153e8f5 Carlo Caione 2019-07-31 203 if (!fw->chip->cmd_shmem_in_base)
2c4ddb215521d5 Carlo Caione 2016-08-27 204 return -EINVAL;
2c4ddb215521d5 Carlo Caione 2016-08-27 205
8cde3c2153e8f5 Carlo Caione 2019-07-31 @206 memcpy(fw->sm_shmem_in_base, buffer, size);
2c4ddb215521d5 Carlo Caione 2016-08-27 207
8cde3c2153e8f5 Carlo Caione 2019-07-31 208 if (meson_sm_call(fw, cmd_index, &written, arg0, arg1, arg2, arg3, arg4) < 0)
2c4ddb215521d5 Carlo Caione 2016-08-27 209 return -EINVAL;
2c4ddb215521d5 Carlo Caione 2016-08-27 210
2c4ddb215521d5 Carlo Caione 2016-08-27 211 if (!written)
2c4ddb215521d5 Carlo Caione 2016-08-27 212 return -EINVAL;
2c4ddb215521d5 Carlo Caione 2016-08-27 213
2c4ddb215521d5 Carlo Caione 2016-08-27 214 return written;
2c4ddb215521d5 Carlo Caione 2016-08-27 215 }
2c4ddb215521d5 Carlo Caione 2016-08-27 216 EXPORT_SYMBOL(meson_sm_call_write);
2c4ddb215521d5 Carlo Caione 2016-08-27 217
:::::: The code at line 206 was first introduced by commit
:::::: 8cde3c2153e8f57be884c0e73f18bc4de150e870 firmware: meson_sm: Rework driver as a proper platform driver
:::::: TO: Carlo Caione <ccaione@baylibre.com>
:::::: CC: Kevin Hilman <khilman@baylibre.com>
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-16 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-16 21:17 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-10-17 20:13 drivers/firmware/meson/meson_sm.c:206:9: sparse: sparse: incorrect type in argument 1 (different address spaces) kernel test robot
2022-10-12 12:06 kernel test robot
2022-07-31 14:50 kernel test robot
2022-06-27 13:08 kernel test robot
2022-04-03 15:08 kernel test robot
2022-03-31 4:19 kernel test robot
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=202207170508.3M7C3ier-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.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.