[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20200127.143159.304887488057743776.davem@davemloft.net>
Date: Mon, 27 Jan 2020 14:31:59 +0100 (CET)
From: David Miller <davem@...emloft.net>
To: daniel@...earbox.net
Cc: jakub.kicinski@...ronome.com, ast@...nel.org,
netdev@...r.kernel.org, bpf@...r.kernel.org
Subject: Re: pull-request: bpf-next 2020-01-27
From: Daniel Borkmann <daniel@...earbox.net>
Date: Mon, 27 Jan 2020 14:06:18 +0100
> The following pull-request contains BPF updates for your *net-next* tree.
>
> We've added 20 non-merge commits during the last 5 day(s) which contain
> a total of 24 files changed, 433 insertions(+), 104 deletions(-).
>
> The main changes are:
>
> 1) Make BPF trampolines and dispatcher aware for the stack unwinder, from Jiri Olsa.
>
> 2) Improve handling of failed CO-RE relocations in libbpf, from Andrii Nakryiko.
>
> 3) Several fixes to BPF sockmap and reuseport selftests, from Lorenz Bauer.
>
> 4) Various cleanups in BPF devmap's XDP flush code, from John Fastabend.
>
> 5) Fix BPF flow dissector when used with port ranges, from Yoshiki Komachi.
>
> 6) Fix bpffs' map_seq_next callback to always inc position index, from Vasily Averin.
>
> 7) Allow overriding LLVM tooling for runqslower utility, from Andrey Ignatov.
>
> 8) Silence false-positive lockdep splats in devmap hash lookup, from Amol Grover.
>
> 9) Fix fentry/fexit selftests to initialize a variable before use, from John Sperbeck.
>
> Please consider pulling these changes from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git
Pulled, thanks Daniel.
Powered by blists - more mailing lists