[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210115172834.25b3c509@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date: Fri, 15 Jan 2021 17:28:34 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: davem@...emloft.net, ast@...nel.org, andrii.nakryiko@...il.com,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf 2021-01-16
On Sat, 16 Jan 2021 01:20:25 +0100 Daniel Borkmann wrote:
> 1) Fix a double bpf_prog_put() for BPF_PROG_{TYPE_EXT,TYPE_TRACING} types in
> link creation's error path causing a refcount underflow, from Jiri Olsa.
>
> 2) Fix BTF validation errors for the case where kernel modules don't declare
> any new types and end up with an empty BTF, from Andrii Nakryiko.
>
> 3) Fix BPF local storage helpers to first check their {task,inode} owners for
> being NULL before access, from KP Singh.
>
> 4) Fix a memory leak in BPF setsockopt handling for the case where optlen is
> zero and thus temporary optval buffer should be freed, from Stanislav Fomichev.
>
> 5) Fix a syzbot memory allocation splat in BPF_PROG_TEST_RUN infra for
> raw_tracepoint caused by too big ctx_size_in, from Song Liu.
>
> 6) Fix LLVM code generation issues with verifier where PTR_TO_MEM{,_OR_NULL}
> registers were spilled to stack but not recognized, from Gilad Reti.
I forgot the bot doesn't reply to bpf PRs.
Pulled, thanks!
Powered by blists - more mailing lists