[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <48BjwD2PG2zB3ws@ozlabs.org>
Date: Tue, 4 Feb 2020 23:01:31 +1100 (AEDT)
From: Michael Ellerman <patch-notifications@...erman.id.au>
To: Alexandre Ghiti <alex@...ti.fr>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
linuxppc-dev@...ts.ozlabs.org, linux-kernel@...r.kernel.org,
Stephen Rothwell <sfr@...b.auug.org.au>,
Alexei Starovoitov <ast@...nel.org>,
linux-next@...r.kernel.org, Zong Li <zong.li@...ive.com>,
Palmer Dabbelt <palmerdabbelt@...gle.com>
Cc: Alexandre Ghiti <alex@...ti.fr>
Subject: Re: [PATCH v2] powerpc: Do not consider weak unresolved symbol relocations as bad
On Sat, 2020-01-18 at 17:03:35 UTC, Alexandre Ghiti wrote:
> Commit 8580ac9404f6 ("bpf: Process in-kernel BTF") introduced two weak
> symbols that may be unresolved at link time which result in an absolute
> relocation to 0. relocs_check.sh emits the following warning:
>
> "WARNING: 2 bad relocations
> c000000001a41478 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_start
> c000000001a41480 R_PPC64_ADDR64 _binary__btf_vmlinux_bin_end"
>
> whereas those relocations are legitimate even for a relocatable kernel
> compiled with -pie option.
>
> relocs_check.sh already excluded some weak unresolved symbols explicitly:
> remove those hardcoded symbols and add some logic that parses the symbols
> using nm, retrieves all the weak unresolved symbols and excludes those from
> the list of the potential bad relocations.
>
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Signed-off-by: Alexandre Ghiti <alex@...ti.fr>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/43e76cd368fbb67e767da5363ffeaa3989993c8c
cheers
Powered by blists - more mailing lists