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
| ||
|
Message-ID: <CAADnVQ+kbxpw7fxRZodTtE7AmEmRDgO9fcmMD8kKRssS8WJizA@mail.gmail.com> Date: Mon, 13 Jan 2020 21:23:50 -0800 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: Zong Li <zong.li@...ive.com> Cc: Alexandre Ghiti <alexandre@...ti.fr>, Palmer Dabbelt <palmerdabbelt@...gle.com>, Stephen Rothwell <sfr@...b.auug.org.au>, Daniel Borkmann <daniel@...earbox.net>, Alexei Starovoitov <ast@...nel.org>, Network Development <netdev@...r.kernel.org>, Linux-Next Mailing List <linux-next@...r.kernel.org>, "linux-kernel@...r.kernel.org List" <linux-kernel@...r.kernel.org>, ppc-dev <linuxppc-dev@...ts.ozlabs.org>, linux-arm-kernel <linux-arm-kernel@...ts.infradead.org> Subject: Re: linux-next: build warning after merge of the bpf-next tree On Sun, Jan 12, 2020 at 8:33 PM Zong Li <zong.li@...ive.com> wrote: > > I'm not quite familiar with btf, so I have no idea why there are two > weak symbols be added in 8580ac9404f6 ("bpf: Process in-kernel BTF") I can explain what these weak symbols are for, but that won't change the fact that compiler or linker are buggy. The weak symbols should work in all cases and compiler should pick correct relocation. In this case it sounds that compiler picked relative relocation and failed to reach zero from that address.
Powered by blists - more mailing lists