Hi Coiby, kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master] [also build test WARNING on v6.9-rc5 next-20240426] [cannot apply to tip/x86/core] [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/Coiby-Xu/kexec_file-allow-to-place-kexec_buf-randomly/20240425-180836 base: linus/master patch link: https://lore.kernel.org/r/20240425100434.198925-3-coxu%40redhat.com patch subject: [PATCH v3 2/7] crash_dump: make dm crypt keys persist for the kdump kernel config: x86_64-randconfig-r113-20240426 (https://download.01.org/0day-ci/archive/20240426/202404262003.qswvgwzu-...@intel.com/config) compiler: gcc-10 (Ubuntu 10.5.0-1ubuntu1) 10.5.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240426/202404262003.qswvgwzu-...@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/202404262003.qswvgwzu-...@intel.com/ sparse warnings: (new ones prefixed by >>) >> kernel/crash_dump_dm_crypt.c:31:3: sparse: sparse: symbol 'keys_header' was >> not declared. Should it be static? vim +/keys_header +31 kernel/crash_dump_dm_crypt.c 27 28 struct keys_header { 29 unsigned int key_count; 30 struct dm_crypt_key keys[] __counted_by(key_count); > 31 } *keys_header; 32 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
