tree: https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/kentry head: fb951a475a1cd1e5e280ee8b4ce64a6a68c77b64 commit: fb951a475a1cd1e5e280ee8b4ce64a6a68c77b64 [11/11] kentry: Verify kentry state in instrumentation_begin/end() config: i386-randconfig-p002-20210518 (attached as .config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0 reproduce (this is a W=1 build): # https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/commit/?id... git remote add luto https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git git fetch --no-tags luto x86/kentry git checkout fb951a475a1cd1e5e280ee8b4ce64a6a68c77b64 # save the attached .config to linux build tree make W=1 ARCH=i386 If you fix the issue, kindly add following tag as appropriate Reported-by: kernel test robot <lkp(a)intel.com&gt; All warnings (new ones prefixed by >>): 60 | void kentry_assert_may_instrument(void) | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ vim +/kentry_assert_may_instrument +60 kernel/entry/common.c 59 61 { 62 DEBUG_ENTRY_WARN_ONCE(this_cpu_read(kentry_cpu_depth) == 0, "instrumentable code is running in the wrong kentry state"); 63 } 64 EXPORT_SYMBOL_GPL(kentry_assert_may_instrument); 65 --- 0-DAY CI Kernel Test Service, Intel Corporation https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org