On Tue, Feb 16, 2021 at 08:55:25AM +0000, Alexander Lobakin wrote: > LKP triggered lots of LD orphan warnings [0]: > > mipsel-linux-ld: warning: orphan section `.data.$Lubsan_data299' from > `init/do_mounts_rd.o' being placed in section `.data.$Lubsan_data299' > mipsel-linux-ld: warning: orphan section `.data.$Lubsan_data183' from > `init/do_mounts_rd.o' being placed in section `.data.$Lubsan_data183' > mipsel-linux-ld: warning: orphan section `.data.$Lubsan_type3' from > `init/do_mounts_rd.o' being placed in section `.data.$Lubsan_type3' > mipsel-linux-ld: warning: orphan section `.data.$Lubsan_type2' from > `init/do_mounts_rd.o' being placed in section `.data.$Lubsan_type2' > mipsel-linux-ld: warning: orphan section `.data.$Lubsan_type0' from > `init/do_mounts_rd.o' being placed in section `.data.$Lubsan_type0' > > [...] > > Seems like "unnamed data" isn't the only type of symbols that UBSAN > instrumentation can emit. > Catch these into .data with the wildcard as well. > > [0] https://lore.kernel.org/linux-mm/202102160741.k57GCNSR-lkp@xxxxxxxxx > > Fixes: f41b233de0ae ("vmlinux.lds.h: catch UBSAN's "unnamed data" into data") > 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(-) applied to mips-next. Thomas. -- Crap can work. Given enough thrust pigs will fly, but it's not necessarily a good idea. [ RFC1925, 2.3 ]
