[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAADnVQ+w_93sZuk-gRbFWYCL9_ocPxD1OmhcCcX3mZ4qD7kayw@mail.gmail.com>
Date: Tue, 14 Jul 2020 10:26:57 -0700
From: Alexei Starovoitov <alexei.starovoitov@...il.com>
To: Jiri Olsa <jolsa@...nel.org>
Cc: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andriin@...com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Geert Uytterhoeven <geert+renesas@...der.be>,
Network Development <netdev@...r.kernel.org>,
bpf <bpf@...r.kernel.org>
Subject: Re: [PATCH 1/2] bpf: Fix build for disabled CONFIG_DEBUG_INFO_BTF option
On Tue, Jul 14, 2020 at 3:25 AM Jiri Olsa <jolsa@...nel.org> wrote:
>
> Stephen reported following linker warnings on powerpc build:
>
> ld: warning: orphan section `.BTF_ids' from `kernel/trace/bpf_trace.o' being placed in section `.BTF_ids'
> ld: warning: orphan section `.BTF_ids' from `kernel/bpf/btf.o' being placed in section `.BTF_ids'
> ld: warning: orphan section `.BTF_ids' from `kernel/bpf/stackmap.o' being placed in section `.BTF_ids'
> ld: warning: orphan section `.BTF_ids' from `net/core/filter.o' being placed in section `.BTF_ids'
> ld: warning: orphan section `.BTF_ids' from `kernel/trace/bpf_trace.o' being placed in section `.BTF_ids'
>
> It's because we generated .BTF_ids section even when
> CONFIG_DEBUG_INFO_BTF is not enabled. Fixing this by
> generating empty btf_id arrays for this case.
>
> Reported-by: Stephen Rothwell <sfr@...b.auug.org.au>
> Tested-by: Geert Uytterhoeven <geert+renesas@...der.be>
> Signed-off-by: Jiri Olsa <jolsa@...nel.org>
Applied both to bpf-next. Thanks for the quick fix.
Powered by blists - more mailing lists