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
| ||
|
Date: Thu, 1 Aug 2019 08:47:03 -0700 From: Alexei Starovoitov <alexei.starovoitov@...il.com> To: Andrii Nakryiko <andriin@...com> Cc: bpf <bpf@...r.kernel.org>, Network Development <netdev@...r.kernel.org>, Alexei Starovoitov <ast@...com>, Daniel Borkmann <daniel@...earbox.net>, Andrey Ignatov <rdna@...com>, Andrii Nakryiko <andrii.nakryiko@...il.com>, Kernel Team <kernel-team@...com> Subject: Re: [PATCH bpf] libbpf: set BTF FD for prog only when there is supported .BTF.ext data On Thu, Aug 1, 2019 at 12:41 AM Andrii Nakryiko <andriin@...com> wrote: > > 5d01ab7bac46 ("libbpf: fix erroneous multi-closing of BTF FD") > introduced backwards-compatibility issue, manifesting itself as -E2BIG > error returned on program load due to unknown non-zero btf_fd attribute > value for BPF_PROG_LOAD sys_bpf() sub-command. > > This patch fixes bug by ensuring that we only ever associate BTF FD with > program if there is a BTF.ext data that was successfully loaded into > kernel, which automatically means kernel supports func_info/line_info > and associated BTF FD for progs (checked and ensured also by BTF > sanitization code). > > Fixes: 5d01ab7bac46 ("libbpf: fix erroneous multi-closing of BTF FD") > Reported-by: Andrey Ignatov <rdna@...com> > Signed-off-by: Andrii Nakryiko <andriin@...com> Applied. Thanks
Powered by blists - more mailing lists