Hi steven, kernel test robot noticed the following build warnings:
[auto build test WARNING on zohar-integrity/next-integrity] [also build test WARNING on linus/master v6.14-rc6 next-20250311] [If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in https://git-scm.com/docs/git-format-patch#_base_tree_information] url: https://github.com/intel-lab-lkp/linux/commits/steven-chen/ima-copy-only-complete-measurement-records-across-kexec/20250305-031719 base: https://git.kernel.org/pub/scm/linux/kernel/git/zohar/linux-integrity.git next-integrity patch link: https://lore.kernel.org/r/20250304190351.96975-5-chenste%40linux.microsoft.com patch subject: [PATCH v9 4/7] ima: kexec: define functions to copy IMA log at soft boot config: powerpc64-randconfig-r133-20250312 (https://download.01.org/0day-ci/archive/20250312/202503121600.imbkp2gc-...@intel.com/config) compiler: powerpc64-linux-gcc (GCC) 14.2.0 reproduce: (https://download.01.org/0day-ci/archive/20250312/202503121600.imbkp2gc-...@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 <l...@intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202503121600.imbkp2gc-...@intel.com/ sparse warnings: (new ones prefixed by >>) security/integrity/ima/ima_kexec.c:107:30: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned short [addressable] [assigned] [usertype] version @@ got restricted __le16 [usertype] @@ security/integrity/ima/ima_kexec.c:107:30: sparse: expected unsigned short [addressable] [assigned] [usertype] version security/integrity/ima/ima_kexec.c:107:30: sparse: got restricted __le16 [usertype] security/integrity/ima/ima_kexec.c:108:28: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [addressable] [assigned] [usertype] count @@ got restricted __le64 [usertype] @@ security/integrity/ima/ima_kexec.c:108:28: sparse: expected unsigned long long [addressable] [assigned] [usertype] count security/integrity/ima/ima_kexec.c:108:28: sparse: got restricted __le64 [usertype] security/integrity/ima/ima_kexec.c:109:34: sparse: sparse: incorrect type in assignment (different base types) @@ expected unsigned long long [addressable] [assigned] [usertype] buffer_size @@ got restricted __le64 [usertype] @@ security/integrity/ima/ima_kexec.c:109:34: sparse: expected unsigned long long [addressable] [assigned] [usertype] buffer_size security/integrity/ima/ima_kexec.c:109:34: sparse: got restricted __le64 [usertype] >> security/integrity/ima/ima_kexec.c:209:23: sparse: sparse: symbol >> 'update_buffer_nb' was not declared. Should it be static? vim +/update_buffer_nb +209 security/integrity/ima/ima_kexec.c 208 > 209 struct notifier_block update_buffer_nb = { 210 .notifier_call = ima_update_kexec_buffer, 211 .priority = 1, 212 }; 213 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
