From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: drivers/crypto/ti/dthev2-common.c:44 dthe_get_dev() warn: can 'dev_data' even be NULL?
Date: Wed, 23 Sep 2026 18:03:57 +0200 [thread overview]
Message-ID: <202609231840.kAb2aFiZ-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
CC: linux-kernel@vger.kernel.org
TO: Herbert Xu <herbert@gondor.apana.org.au>
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: fe2ec83746e501645709761605c2464a44fd2929
commit: 35c5097f737a164b3afe23d07698db95061f0db8 crypto: ti - Enable compile testing for dthev2
date: 1 year, 1 month ago
:::::: branch date: 23 hours ago
:::::: commit date: 1 year, 1 month ago
config: m68k-randconfig-r2201-20260923 (https://download.01.org/0day-ci/archive/20260923/202609231840.kAb2aFiZ-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 11.5.0
smatch: v0.5.0-9187-g5189e3fb
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
| Fixes: 35c5097f737a ("crypto: ti - Enable compile testing for dthev2")
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202609231840.kAb2aFiZ-lkp@intel.com/
smatch warnings:
drivers/crypto/ti/dthev2-common.c:44 dthe_get_dev() warn: can 'dev_data' even be NULL?
vim +/dev_data +44 drivers/crypto/ti/dthev2-common.c
52f641bc63a466 T Pratham 2025-08-20 34
52f641bc63a466 T Pratham 2025-08-20 35 struct dthe_data *dthe_get_dev(struct dthe_tfm_ctx *ctx)
52f641bc63a466 T Pratham 2025-08-20 36 {
52f641bc63a466 T Pratham 2025-08-20 37 struct dthe_data *dev_data;
52f641bc63a466 T Pratham 2025-08-20 38
52f641bc63a466 T Pratham 2025-08-20 39 if (ctx->dev_data)
52f641bc63a466 T Pratham 2025-08-20 40 return ctx->dev_data;
52f641bc63a466 T Pratham 2025-08-20 41
52f641bc63a466 T Pratham 2025-08-20 42 spin_lock_bh(&dthe_dev_list.lock);
52f641bc63a466 T Pratham 2025-08-20 43 dev_data = list_first_entry(&dthe_dev_list.dev_list, struct dthe_data, list);
52f641bc63a466 T Pratham 2025-08-20 @44 if (dev_data)
52f641bc63a466 T Pratham 2025-08-20 45 list_move_tail(&dev_data->list, &dthe_dev_list.dev_list);
52f641bc63a466 T Pratham 2025-08-20 46 spin_unlock_bh(&dthe_dev_list.lock);
52f641bc63a466 T Pratham 2025-08-20 47
52f641bc63a466 T Pratham 2025-08-20 48 return dev_data;
52f641bc63a466 T Pratham 2025-08-20 49 }
52f641bc63a466 T Pratham 2025-08-20 50
:::::: The code at line 44 was first introduced by commit
:::::: 52f641bc63a46657b1d72d902fcee30ab1233c7b crypto: ti - Add driver for DTHE V2 AES Engine (ECB, CBC)
:::::: TO: T Pratham <t-pratham@ti.com>
:::::: CC: Herbert Xu <herbert@gondor.apana.org.au>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-09-23 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-23 16:03 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-11 11:10 drivers/crypto/ti/dthev2-common.c:44 dthe_get_dev() warn: can 'dev_data' even be NULL? kernel test robot
2026-06-11 11:19 ` Dan Carpenter
2025-12-18 5:24 kernel test robot
2025-12-18 7:19 ` Dan Carpenter
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=202609231840.kAb2aFiZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@lists.linux.dev \
/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.