tree: https://gitee.com/openeuler/kernel.git OLK-6.6 head: 04473ee9ed912a16fff0d8846ad565bbf3d63c77 commit: e2a8f20dd8e9df695f736e51cd9115ae55be92d1 [3547/3547] Crash: add lock to serialize crash hotplug handling config: x86_64-randconfig-122-20251217 (https://download.01.org/0day-ci/archive/20251220/202512202121.96JSWGZX-lkp@i...) compiler: gcc-14 (Debian 14.2.0-19) 14.2.0 reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251220/202512202121.96JSWGZX-lkp@i...) 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/202512202121.96JSWGZX-lkp@intel.com/ sparse warnings: (new ones prefixed by >>)

...

kernel/crash_core.c:749:1: sparse: sparse: symbol '__crash_hotplug_lock' was not declared. Should it be static?

vim +/__crash_hotplug_lock +749 kernel/crash_core.c 741 742 /* 743 * Different than kexec/kdump loading/unloading/jumping/shrinking which 744 * usually rarely happen, there will be many crash hotplug events notified 745 * during one short period, e.g one memory board is hot added and memory 746 * regions are online. So mutex lock __crash_hotplug_lock is used to 747 * serialize the crash hotplug handling specifically. 748 */

749 DEFINE_MUTEX(__crash_hotplug_lock); 750 #define crash_hotplug_lock() mutex_lock(&__crash_hotplug_lock) 751 #define crash_hotplug_unlock() mutex_unlock(&__crash_hotplug_lock) 752

-- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki