From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: Re: [PATCH v11 3/9] tee: implement protected DMA-heap
Date: Sat, 16 Aug 2025 16:35:43 +0800 [thread overview]
Message-ID: <202508161645.gRvuwznK-lkp@intel.com> (raw)
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
In-Reply-To: <20250813060339.2977604-4-jens.wiklander@linaro.org>
References: <20250813060339.2977604-4-jens.wiklander@linaro.org>
TO: Jens Wiklander <jens.wiklander@linaro.org>
Hi Jens,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 038d61fd642278bab63ee8ef722c50d10ab01e8f]
url: https://github.com/intel-lab-lkp/linux/commits/Jens-Wiklander/optee-sync-secure-world-ABI-headers/20250813-140602
base: 038d61fd642278bab63ee8ef722c50d10ab01e8f
patch link: https://lore.kernel.org/r/20250813060339.2977604-4-jens.wiklander%40linaro.org
patch subject: [PATCH v11 3/9] tee: implement protected DMA-heap
:::::: branch date: 3 days ago
:::::: commit date: 3 days ago
config: alpha-randconfig-r071-20250816 (https://download.01.org/0day-ci/archive/20250816/202508161645.gRvuwznK-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 10.5.0
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>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202508161645.gRvuwznK-lkp@intel.com/
smatch warnings:
drivers/tee/tee_heap.c:327 tee_device_put_all_dma_heaps() warn: iterator 'i' not incremented
vim +/i +327 drivers/tee/tee_heap.c
47438b4ab89c8e Jens Wiklander 2025-08-13 321
47438b4ab89c8e Jens Wiklander 2025-08-13 322 void tee_device_put_all_dma_heaps(struct tee_device *teedev)
47438b4ab89c8e Jens Wiklander 2025-08-13 323 {
47438b4ab89c8e Jens Wiklander 2025-08-13 324 struct tee_dma_heap *h;
47438b4ab89c8e Jens Wiklander 2025-08-13 325 u_long i;
47438b4ab89c8e Jens Wiklander 2025-08-13 326
47438b4ab89c8e Jens Wiklander 2025-08-13 @327 xa_for_each(&tee_dma_heap, i, h) {
47438b4ab89c8e Jens Wiklander 2025-08-13 328 if (h) {
47438b4ab89c8e Jens Wiklander 2025-08-13 329 mutex_lock(&h->mu);
47438b4ab89c8e Jens Wiklander 2025-08-13 330 if (h->teedev == teedev && !h->shutting_down) {
47438b4ab89c8e Jens Wiklander 2025-08-13 331 h->shutting_down = true;
47438b4ab89c8e Jens Wiklander 2025-08-13 332 put_tee_heap(h);
47438b4ab89c8e Jens Wiklander 2025-08-13 333 }
47438b4ab89c8e Jens Wiklander 2025-08-13 334 mutex_unlock(&h->mu);
47438b4ab89c8e Jens Wiklander 2025-08-13 335 }
47438b4ab89c8e Jens Wiklander 2025-08-13 336 }
47438b4ab89c8e Jens Wiklander 2025-08-13 337 }
47438b4ab89c8e Jens Wiklander 2025-08-13 338 EXPORT_SYMBOL_GPL(tee_device_put_all_dma_heaps);
47438b4ab89c8e Jens Wiklander 2025-08-13 339
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-08-16 8:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-16 8:35 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-13 6:02 [PATCH v11 0/9] TEE subsystem for protected dma-buf allocations Jens Wiklander
2025-08-13 6:02 ` [PATCH v11 3/9] tee: implement protected DMA-heap Jens Wiklander
2025-08-13 6:02 ` Jens Wiklander
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=202508161645.gRvuwznK-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.