On 4/3/24 3:34 PM, kernel test robot wrote: > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > head: 727900b675b749c40ba1f6669c7ae5eb7eb8e837 > commit: 68cd017e43dd5657fd2875b38da5933e1fa7660c [3501/3504] Merge branch 'slab/for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/vbabka/slab.git > config: riscv-randconfig-r032-20221115 (https://download.01.org/0day-ci/archive/20240403/202404032101.sKzRXCWH-lkp@xxxxxxxxx/config) > compiler: riscv32-linux-gcc (GCC) 13.2.0 > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240403/202404032101.sKzRXCWH-lkp@xxxxxxxxx/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 <lkp@xxxxxxxxx> > | Closes: https://lore.kernel.org/oe-kbuild-all/202404032101.sKzRXCWH-lkp@xxxxxxxxx/ > > All errors (new ones prefixed by >>): > >>> riscv32-linux-ld: section .data LMA [001f9000,009465d7] overlaps section .text LMA [000a7e84,0177d68b] > riscv32-linux-ld: section .pci_fixup VMA [c2167be0,c216a82f] overlaps section .data VMA [c2000000,c274d5d7] Hm I don't really see how the slab/for-next could cause this. Could it be false positive?
