From: Thomas Bogendoerfer <tsbogend@xxxxxxxxxxxxxxxx> Date: Tue, 23 Feb 2021 13:21:44 +0100 > On Tue, Feb 23, 2021 at 11:36:41AM +0000, Alexander Lobakin wrote: > > > LKP caught another bunch of orphaned instrumentation symbols [0]: > > > > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > > `init/main.o' being placed in section `.data.$LPBX1' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > > `init/main.o' being placed in section `.data.$LPBX0' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > > `init/do_mounts.o' being placed in section `.data.$LPBX1' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > > `init/do_mounts.o' being placed in section `.data.$LPBX0' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > > `init/do_mounts_initrd.o' being placed in section `.data.$LPBX1' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > > `init/do_mounts_initrd.o' being placed in section `.data.$LPBX0' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > > `init/initramfs.o' being placed in section `.data.$LPBX1' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > > `init/initramfs.o' being placed in section `.data.$LPBX0' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX1' from > > > `init/calibrate.o' being placed in section `.data.$LPBX1' > > > mipsel-linux-ld: warning: orphan section `.data.$LPBX0' from > > > `init/calibrate.o' being placed in section `.data.$LPBX0' > > > > > > [...] > > > > > > Soften the wildcard to .data.$L* to grab these ones into .data too. > > > > > > [0] https://lore.kernel.org/lkml/202102231519.lWPLPveV-lkp@xxxxxxxxx > > > > > > Reported-by: kernel test robot <lkp@xxxxxxxxx> > > > Signed-off-by: Alexander Lobakin <alobakin@xxxxx> > > > --- > > > include/asm-generic/vmlinux.lds.h | 2 +- > > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > Hi Thomas, > > > > This applies on top of mips-next or Linus' tree, so you may need to > > rebase mips-fixes before taking it. > > It's not for mips-next as it should go into this cycle as a [hot]fix. > > I haven't added any "Fixes:" tag since these warnings is a result > > of merging several sets and of certain build configurations that > > almost couldn't be tested separately. > > no worries, mips-fixes is defunct during merge windows. I'll send another > pull request to Linus and will add this patch to it. Ah, thank you! > Thomas. Al > -- > Crap can work. Given enough thrust pigs will fly, but it's not necessarily a > good idea. [ RFC1925, 2.3 ]
