From: kernel test robot <lkp@intel.com>
To: Vabhav Sharma <vabhav.sharma@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
linux-imx@nxp.com, Ulf Hansson <ulf.hansson@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Iuliana Prodan <iuliana.prodan@nxp.com>
Cc: oe-kbuild-all@lists.linux.dev,
Silvano Di Ninno <silvano.dininno@nxp.com>,
Varun Sethi <V.Sethi@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>, Peng Fan <peng.fan@nxp.com>,
Dong Aisheng <aisheng.dong@nxp.com>,
frank.li@nxp.com, daniel.baluta@nxp.com,
Vabhav Sharma <vabhav.sharma@nxp.com>,
Franck LENORMAND <franck.lenormand@nxp.com>
Subject: Re: [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW
Date: Thu, 2 May 2024 08:54:44 +0800 [thread overview]
Message-ID: <202405020818.2mTfooXt-lkp@intel.com> (raw)
In-Reply-To: <20240501053205.1737248-4-vabhav.sharma@nxp.com>
Hi Vabhav,
kernel test robot noticed the following build warnings:
[auto build test WARNING on shawnguo/for-next]
[also build test WARNING on robh/for-next krzk/for-next krzk-dt/for-next linus/master v6.9-rc6 next-20240501]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Vabhav-Sharma/dt-bindings-firmware-secvio-Add-documentation/20240501-133607
base: https://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux.git for-next
patch link: https://lore.kernel.org/r/20240501053205.1737248-4-vabhav.sharma%40nxp.com
patch subject: [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW
config: hexagon-randconfig-r131-20240502 (https://download.01.org/0day-ci/archive/20240502/202405020818.2mTfooXt-lkp@intel.com/config)
compiler: clang version 19.0.0git (https://github.com/llvm/llvm-project 37ae4ad0eef338776c7e2cffb3896153d43dcd90)
reproduce: (https://download.01.org/0day-ci/archive/20240502/202405020818.2mTfooXt-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/202405020818.2mTfooXt-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/soc/imx/secvio/imx-secvio-sc.c:381:37: sparse: sparse: incorrect type in argument 1 (different address spaces) @@ expected void [noderef] __user *to @@ got void * @@
drivers/soc/imx/secvio/imx-secvio-sc.c:381:37: sparse: expected void [noderef] __user *to
drivers/soc/imx/secvio/imx-secvio-sc.c:381:37: sparse: got void *
>> drivers/soc/imx/secvio/imx-secvio-sc.c:393:46: sparse: sparse: incorrect type in argument 2 (different address spaces) @@ expected void const [noderef] __user *from @@ got void * @@
drivers/soc/imx/secvio/imx-secvio-sc.c:393:46: sparse: expected void const [noderef] __user *from
drivers/soc/imx/secvio/imx-secvio-sc.c:393:46: sparse: got void *
vim +381 drivers/soc/imx/secvio/imx-secvio-sc.c
368
369 static long imx_secvio_sc_ioctl(struct file *file, unsigned int cmd, unsigned long arg)
370 {
371 struct device *dev = file->private_data;
372 struct secvio_sc_notifier_info info;
373 int ret;
374
375 switch (cmd) {
376 case IMX_SECVIO_SC_GET_STATE:
377 ret = imx_secvio_sc_get_state(dev, &info);
378 if (ret)
379 return ret;
380
> 381 ret = copy_to_user((void *)arg, &info, sizeof(info));
382 if (ret) {
383 dev_err(dev, "Fail to copy info to user\n");
384 return -EFAULT;
385 }
386 break;
387 case IMX_SECVIO_SC_CHECK_STATE:
388 ret = imx_secvio_sc_check_state(dev);
389 if (ret)
390 return ret;
391 break;
392 case IMX_SECVIO_SC_CLEAR_STATE:
> 393 ret = copy_from_user(&info, (void *)arg, sizeof(info));
394 if (ret) {
395 dev_err(dev, "Fail to copy info from user\n");
396 return -EFAULT;
397 }
398
399 ret = imx_secvio_sc_clear_state(dev, info.hpsvs, info.lps,
400 info.lptds);
401 if (ret)
402 return ret;
403 break;
404 default:
405 ret = -ENOIOCTLCMD;
406 }
407
408 return ret;
409 }
410
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-05-02 0:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 5:32 [PATCH 0/4] soc: imx: secvio: Add secvio support Vabhav Sharma
2024-05-01 5:32 ` [PATCH 1/4] dt-bindings: firmware: secvio: Add documentation Vabhav Sharma
2024-05-01 9:46 ` Krzysztof Kozlowski
2024-05-09 4:04 ` [EXT] " Vabhav Sharma
2024-05-01 5:32 ` [PATCH 2/4] firmware: imx: Add SC APIs required for secvio module Vabhav Sharma
2024-05-01 5:32 ` [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW Vabhav Sharma
2024-05-02 0:54 ` kernel test robot [this message]
2024-05-01 5:32 ` [PATCH 4/4] arm64: dts: imx8q: Add node for Security Violation Vabhav Sharma
-- strict thread matches above, loose matches on Subject: below --
2024-05-09 0:45 [PATCH 0/4] soc: imx: secvio: Add secvio support Vabhav Sharma
2024-05-09 0:45 ` [PATCH 3/4] soc: imx: secvio: Add support for SNVS secvio and tamper via SCFW Vabhav Sharma
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=202405020818.2mTfooXt-lkp@intel.com \
--to=lkp@intel.com \
--cc=V.Sethi@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=conor+dt@kernel.org \
--cc=daniel.baluta@nxp.com \
--cc=festevam@gmail.com \
--cc=franck.lenormand@nxp.com \
--cc=frank.li@nxp.com \
--cc=iuliana.prodan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pankaj.gupta@nxp.com \
--cc=peng.fan@nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.com \
--cc=ulf.hansson@linaro.org \
--cc=vabhav.sharma@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;
as well as URLs for NNTP newsgroup(s).