lkml.org 
[lkml]   [2021]   [Feb]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH mips-fixes] vmlinux.lds.h: catch even more instrumentation symbols into .data
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@intel.com
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Signed-off-by: Alexander Lobakin <alobakin@pm.me>
> > ---
> > 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.

Thomas.

--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]

\
 
 \ /
  Last update: 2021-02-23 14:01    [W:0.038 / U:5.504 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site