Hi Wonhyuk, On Tue, Dec 22, 2020 at 04:07:59AM +0800, kernel test robot wrote: > Hi Wonhyuk, > > FYI, the error/warning still remains. > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: 4c6ed015c2a57c3b385265895a69a87f87da8e28 > commit: 6c207504ae7937ac70a1d753c250eb6ab125d70e [1888/14054] percpu: reduce the number of cpu distance comparisons > config: x86_64-randconfig-a013-20201221 (attached as .config) > compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project cee1e7d14f4628d6174b33640d502bff3b54ae45) > reproduce (this is a W=1 build): > wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross > chmod +x ~/bin/make.cross > # install x86_64 cross compiling tool for clang build > # apt-get install binutils-x86-64-linux-gnu > # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=6c207504ae7937ac70a1d753c250eb6ab125d70e > git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git > git fetch --no-tags linux-next master > git checkout 6c207504ae7937ac70a1d753c250eb6ab125d70e > # save the attached .config to linux build tree > COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64 > > If you fix the issue, kindly add following tag as appropriate > Reported-by: kernel test robot <lkp@xxxxxxxxx> > > All warnings (new ones prefixed by >>, old ones prefixed by <<): > > >> WARNING: modpost: vmlinux.o(.text+0x50f236): Section mismatch in reference from the function cpumask_clear_cpu() to the variable .init.data:pcpu_build_alloc_info.mask > The function cpumask_clear_cpu() references > the variable __initdata pcpu_build_alloc_info.mask. > This is often because cpumask_clear_cpu lacks a __initdata > annotation or the annotation of pcpu_build_alloc_info.mask is wrong. > > --- > 0-DAY CI Kernel Test Service, Intel Corporation > https://lists.01.org/hyperkitty/list/kbuild-all@xxxxxxxxxxxx This is my fault, I didn't have time to look into this until recently. The issue is that the second call to cpumask_clear_cpu() is not being inlined resulting in the warning above. Because this is purely a qol fix, I'm going to move this from for-5.11 to for-5.12 and figure out the best way to fix this warning. Thanks, Dennis
