From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18 1/1] arch/arm64/kvm/hyp/nvhe/pkvm.c:1906:40: sparse: sparse: cast to restricted __le32
Date: Fri, 06 Feb 2026 16:47:13 +0800 [thread overview]
Message-ID: <202602061656.HTIBEG7j-lkp@intel.com> (raw)
tree: https://android.googlesource.com/kernel/common android17-6.18
head: 367ce0597211847ec0f62618e0a515f37cc84dd6
commit: eff36ac2fe9748dfe31b22d00b62f6eaf7323732 [1/1] ANDROID: KVM: arm64: Add TRNG handling for protected guests
config: arm64-randconfig-r134-20260205 (https://download.01.org/0day-ci/archive/20260206/202602061656.HTIBEG7j-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 13.4.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260206/202602061656.HTIBEG7j-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/202602061656.HTIBEG7j-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
arch/arm64/kvm/hyp/nvhe/pkvm.c:248:1: sparse: sparse: symbol 'vm_table_lock' was not declared. Should it be static?
>> arch/arm64/kvm/hyp/nvhe/pkvm.c:1906:40: sparse: sparse: cast to restricted __le32
arch/arm64/kvm/hyp/nvhe/pkvm.c:1907:34: sparse: sparse: cast to restricted __le32
arch/arm64/kvm/hyp/nvhe/pkvm.c:1908:34: sparse: sparse: cast to restricted __le32
arch/arm64/kvm/hyp/nvhe/pkvm.c:1909:34: sparse: sparse: cast to restricted __le32
vim +1906 arch/arm64/kvm/hyp/nvhe/pkvm.c
1879
1880 static bool module_handle_guest_trng(struct kvm_vcpu *vcpu)
1881 {
1882 u32 fn;
1883 u64 ret = SMCCC_RET_NOT_SUPPORTED;
1884 const uuid_t *uuid;
1885
1886 fn = smccc_get_function(vcpu);
1887 uuid = module_get_guest_trng_uuid();
1888 if (!uuid)
1889 return false;
1890
1891 switch (fn) {
1892 case ARM_SMCCC_TRNG_VERSION:
1893 ret = ARM_SMCCC_TRNG_VER_1_0;
1894 break;
1895 case ARM_SMCCC_TRNG_FEATURES:
1896 switch (smccc_get_arg1(vcpu)) {
1897 case ARM_SMCCC_TRNG_VERSION:
1898 case ARM_SMCCC_TRNG_FEATURES:
1899 case ARM_SMCCC_TRNG_GET_UUID:
1900 case ARM_SMCCC_TRNG_RND64:
1901 ret = SMCCC_RET_SUCCESS;
1902 break;
1903 }
1904 break;
1905 case ARM_SMCCC_TRNG_GET_UUID:
> 1906 smccc_set_retval(vcpu, le32_to_cpu(((u32 *)uuid->b)[0]),
1907 le32_to_cpu(((u32 *)uuid->b)[1]),
1908 le32_to_cpu(((u32 *)uuid->b)[2]),
1909 le32_to_cpu(((u32 *)uuid->b)[3]));
1910 return true;
1911 case ARM_SMCCC_TRNG_RND64:
1912 return module_handle_guest_trng_rng(vcpu);
1913 default:
1914 return false;
1915 }
1916
1917 smccc_set_retval(vcpu, ret, 0, 0, 0);
1918 return true;
1919 }
1920
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-02-06 8:47 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=202602061656.HTIBEG7j-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@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.