riscv: Stop considering R_RISCV_NONE as bad relocationsEven though those relocations should not be present in the finalvmlinux, there are a lot of them. And since those relocations areconsidered
riscv: Stop considering R_RISCV_NONE as bad relocationsEven though those relocations should not be present in the finalvmlinux, there are a lot of them. And since those relocations areconsidered "bad", they flood the compilation output which may hide somelegitimate bad relocations.Signed-off-by: Alexandre Ghiti <alexghiti@rivosinc.com>Tested-by: Ron Economos <re@w6rz.net>Link: https://lore.kernel.org/r/20250710-dev-alex-riscv_none_bad_relocs_v1-v1-1-758f2fcc6e75@rivosinc.comSigned-off-by: Palmer Dabbelt <palmer@dabbelt.com>
show more ...
riscv: Check relocations at compile timeRelocating kernel at runtime is done very early in the boot process, soit is not convenient to check for relocations there and react in case arelocation wa
riscv: Check relocations at compile timeRelocating kernel at runtime is done very early in the boot process, soit is not convenient to check for relocations there and react in case arelocation was not expected.There exists a script in scripts/ that extracts the relocations fromvmlinux that is then used at postlink to check the relocations.Signed-off-by: Alexandre Ghiti <alex@ghiti.fr>Reviewed-by: Anup Patel <anup@brainfault.org>Link: https://lore.kernel.org/r/20230329045329.64565-6-alexghiti@rivosinc.comSigned-off-by: Palmer Dabbelt <palmer@rivosinc.com>