linux-kernel - Re: [rust:rust-next 2/24] ld.lld: error: kernel/built-in.a(kallsyms.o):(function get_symbol_offset: .text+0x5f0): relocation R_RISCV_PCREL_HI20 out of range: -524435 is not in [-524288, 524287]; references kallsyms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <d4c31c67-de25-ac88-7115-4872e31f8bdf@intel.com>
Date:   Sat, 4 Jun 2022 18:14:27 +0800
From:   Yujie Liu <yujie.liu@...el.com>
To:     Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
CC:     Miguel Ojeda <ojeda@...nel.org>, <kbuild-all@...ts.01.org>,
        <llvm@...ts.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [rust:rust-next 2/24] ld.lld: error:
 kernel/built-in.a(kallsyms.o):(function get_symbol_offset: .text+0x5f0):
 relocation R_RISCV_PCREL_HI20 out of range: -524435 is not in [-524288,
 524287]; references kallsyms_names

On 6/3/2022 19:01, Miguel Ojeda wrote:
> On Fri, Jun 3, 2022 at 12:32 PM kernel test robot <yujie.liu@...el.com> wrote:
>>
>>   >> ld.lld: error: kernel/built-in.a(kallsyms.o):(function get_symbol_offset: .text+0x5f0): relocation R_RISCV_PCREL_HI20 out of range: -524435 is not in [-524288, 524287]; references kallsyms_names
>>      >>> referenced by kallsyms.c
>>      >>> defined in kernel/built-in.a(kallsyms.o)
> 
> There are similar reports for the same relocation type in trees
> without Rust support merged, so this might not be being triggered by
> Rust itself, e.g.:
> 
>      https://lore.kernel.org/llvm/202206010956.rOpdU4dr-lkp@intel.com/
>      https://lore.kernel.org/llvm/202205280837.PPVZBhXr-lkp@intel.com/

Thanks for the info, it looks like an existing relocation issue in
kallsyms under riscv arch.

commit 2087d6ac3567b (kallsyms: support "big" kernel symbols) changed
some code of kallsyms to support long Rust symbols, so it exposed that
relocation issue and triggered this report.

We'll do more checks next time to ensure the reported issue is indeed
Rust related.

Thanks,
Yujie

> 
> Cheers,
> Miguel