On Wed, Jul 10, 2024 at 05:32:51PM -0700, SeongJae Park wrote: > Hello, > > On Tue, 9 Jul 2024 05:52:19 +0800 kernel test robot <lkp@xxxxxxxxx> wrote: > > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > > head: 0b58e108042b0ed28a71cd7edf5175999955b233 > > commit: c3bf782bb0fffebcc4e467033cf6bf5e5e1b0784 [7416/10451] mm: make alloc_demote_folio externally invokable for migration > > config: riscv-randconfig-r033-20230517 (https://download.01.org/0day-ci/archive/20240709/202407090506.BxtnYHgZ-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/20240709/202407090506.BxtnYHgZ-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/202407090506.BxtnYHgZ-lkp@xxxxxxxxx/ > > > > All warnings (new ones prefixed by >>, old ones prefixed by <<): > > > [...] > > >> WARNING: modpost: vmlinux: section mismatch in reference: svc_xprt_create_from_sa+0x6e (section: .text) -> .L96 (section: .init.text) > > Thank you for this report. However, given the diff of Honggyu's commit, it > doesn't seem to be the real root cause of this issue. I also confirmed the > warning is not reproducible with the commit on mm-unstable. > > Please let me know if I'm missing something. Sorry for the false positive, this is a wrong report which seems to only occur on riscv arch. The bot will be fixed to avoid sending this kind of issues. Sorry again for the trouble. > > > Thanks, > SJ > > [...] >
