From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-lts:5.4/preempt-rt 9719/19036] drivers/crypto/keembay/keembay-ocs-hcu-core.c:218:31: sparse: sparse: Using plain integer as NULL pointer
Date: Sun, 24 Oct 2021 18:23:24 +0800 [thread overview]
Message-ID: <202110241820.2S6d1fUC-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2335 bytes --]
tree: https://github.com/intel/linux-intel-lts.git 5.4/preempt-rt
head: 646a89c49751509d6493602ca6df16e229574d24
commit: 9b07a958f2eb496c88faf0bd749eb600357f4190 [9719/19036] crypto: keembay: Add Keem Bay OCS HCU
config: x86_64-randconfig-s021-20211001 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.4-dirty
# https://github.com/intel/linux-intel-lts/commit/9b07a958f2eb496c88faf0bd749eb600357f4190
git remote add intel-lts https://github.com/intel/linux-intel-lts.git
git fetch --no-tags intel-lts 5.4/preempt-rt
git checkout 9b07a958f2eb496c88faf0bd749eb600357f4190
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/crypto/keembay/
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/crypto/keembay/keembay-ocs-hcu-core.c:218:31: sparse: sparse: Using plain integer as NULL pointer
drivers/crypto/keembay/keembay-ocs-hcu-core.c:219:31: sparse: sparse: Using plain integer as NULL pointer
drivers/crypto/keembay/keembay-ocs-hcu-core.c:749:31: sparse: sparse: Using plain integer as NULL pointer
drivers/crypto/keembay/keembay-ocs-hcu-core.c:750:31: sparse: sparse: Using plain integer as NULL pointer
vim +218 drivers/crypto/keembay/keembay-ocs-hcu-core.c
202
203 static void kmb_ocs_free_dma_list(struct ocs_hcu_rctx *rctx)
204 {
205 struct ocs_hcu_dev *hcu_dev = rctx->hcu_dev;
206 struct device *dev = hcu_dev->dev;
207
208 if (!rctx->dma_list_head || !rctx->dma_list_tail)
209 return;
210
211 if (rctx->sg_dma_nents > 0)
212 dma_unmap_sg(dev, hcu_dev->req->src, rctx->sg_dma_nents,
213 DMA_TO_DEVICE);
214
215 dma_free_coherent(dev, rctx->dma_list_size, rctx->dma_list_head,
216 rctx->ll_dma_addr);
217
> 218 rctx->dma_list_head = 0;
219 rctx->dma_list_tail = 0;
220 rctx->ll_dma_addr = 0;
221 }
222
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 36209 bytes --]
next reply other threads:[~2021-10-24 10:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 10:23 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-25 0:38 [intel-lts:5.4/preempt-rt 9719/19036] drivers/crypto/keembay/keembay-ocs-hcu-core.c:218:31: sparse: sparse: Using plain integer as NULL pointer kernel test robot
2021-10-24 5:07 kernel test robot
2021-10-22 3:46 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=202110241820.2S6d1fUC-lkp@intel.com \
--to=lkp@intel.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.