summaryrefslogtreecommitdiffstats
path: root/drivers/char
diff options
context:
space:
mode:
authorAlexander Lobakin <alobakin@pm.me>2021-02-16 09:55:25 +0100
committerThomas Bogendoerfer <tsbogend@alpha.franken.de>2021-02-16 17:10:48 +0100
commitfa07eca8d8c6567e0f5a8d36dcf776fa0aa2f6f4 (patch)
tree18035171643e8c5fcdb27debc066829b22c792cc /drivers/char
parentMIPS: kernel: Drop kgdb_call_nmi_hook (diff)
downloadlinux-fa07eca8d8c6567e0f5a8d36dcf776fa0aa2f6f4.tar.xz
linux-fa07eca8d8c6567e0f5a8d36dcf776fa0aa2f6f4.zip
vmlinux.lds.h: catch more UBSAN symbols into .data
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@intel.com Fixes: f41b233de0ae ("vmlinux.lds.h: catch UBSAN's "unnamed data" into data") Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Alexander Lobakin <alobakin@pm.me> Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Diffstat (limited to 'drivers/char')
0 files changed, 0 insertions, 0 deletions