From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com
Subject: [android-common:android17-6.18 1/1] drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:44:16: sparse: sparse: not a function list_add_valid_or_report
Date: Sat, 11 Apr 2026 15:23:36 +0800 [thread overview]
Message-ID: <202604111520.aI0TP518-lkp@intel.com> (raw)
::::::
:::::: Manual check reason: "low confidence static check first_new_problem: drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:44:16: sparse: sparse: not a function list_add_valid_or_report"
::::::
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
Hi Mostafa,
First bad commit (maybe != root cause):
tree: https://android.googlesource.com/kernel/common android17-6.18
head: 4e4a75829357064389709ce8601610646d9c1391
commit: 2ea2104b7c2ba0bed9782bc4236746e850e1bb33 [1/1] ANDROID: iommu/arm-smmu-v3-kvm-pv: Add host driver for pKVM
:::::: branch date: 14 hours ago
:::::: commit date: 4 months ago
config: arm64-randconfig-r133-20260408 (https://download.01.org/0day-ci/archive/20260411/202604111520.aI0TP518-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project c80443cd37b2e2788cba67ffa180a6331e5f0791)
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260411/202604111520.aI0TP518-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/r/202604111520.aI0TP518-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:44:16: sparse: sparse: not a function list_add_valid_or_report
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:49:16: sparse: sparse: not a function list_del_entry_valid_or_report
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:284:25: sparse: sparse: restricted __le64 degrades to integer
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:460:22: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 @@ got unsigned long long @@
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:464:22: sparse: sparse: incorrect type in assignment (different base types) @@ expected restricted __le64 @@ got unsigned long long @@
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:495:13: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] val @@ got restricted __le64 @@
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:526:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:528:21: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [usertype] @@ got restricted __le64 [usertype] @@
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:544:9: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long volatile @@ got restricted __le64 [usertype] @@
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:601:37: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:608:37: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:608:37: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:615:31: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:620:37: sparse: sparse: cast to restricted __le64
drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:620:37: sparse: sparse: cast to restricted __le64
>> drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c:1074:27: sparse: sparse: incorrect type in assignment (different address spaces) @@ expected void [noderef] __iomem *base @@ got void * @@
vim +44 drivers/iommu/arm/arm-smmu-v3/pkvm/pv/arm-smmu-v3-pv.c
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 34
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 35 void *__memset(void *dst, int c, size_t count)
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 36 {
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 37 return memset(dst, c, count);
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 38 }
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 39 #ifdef CONFIG_LIST_HARDENED
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 40 bool __list_add_valid_or_report(struct list_head *new,
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 41 struct list_head *prev,
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 42 struct list_head *next)
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 43 {
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 @44 return CALL_FROM_OPS(list_add_valid_or_report, new, prev, next);
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 45 }
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 46
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 47 bool __list_del_entry_valid_or_report(struct list_head *entry)
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 48 {
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 @49 return CALL_FROM_OPS(list_del_entry_valid_or_report, entry);
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 50 }
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 51 #endif
5b5ca4a5251ec53 Mostafa Saleh 2025-10-13 52
:::::: The code at line 44 was first introduced by commit
:::::: 5b5ca4a5251ec5381b425f2a8e5ea32c59175561 ANDROID: iommu/arm-smmu-v3-kvm-pv: Introduce pKVM SMMUv3 PV driver
:::::: TO: Mostafa Saleh <smostafa@google.com>
:::::: CC: Mostafa Saleh <smostafa@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-11 7:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202604111520.aI0TP518-lkp@intel.com \
--to=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox