From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org
Subject: pull-request: bpf 2017-12-13
Date: Wed, 13 Dec 2017 23:19:12 +0100 [thread overview]
Message-ID: <20171213221912.6036-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Addition of explicit scheduling points to map alloc/free
in order to avoid having to hold the CPU for too long,
from Eric.
2) Fixing of a corruption in overlapping perf_event_output
calls from different BPF prog types on the same CPU out
of different contexts, from Daniel.
3) Fallout fixes for recent correction of broken uapi for
BPF_PROG_TYPE_PERF_EVENT. um had a missing asm header
that needed to be pulled in from asm-generic and for
BPF selftests the asm-generic include did not work,
so similar asm include scheme was adapted for that
problematic header that perf is having with other
header files under tools, from Daniel.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Thanks a lot!
----------------------------------------------------------------
The following changes since commit 30791ac41927ebd3e75486f9504b6d2280463bf0:
tcp md5sig: Use skb's saddr when replying to an incoming segment (2017-12-12 11:15:42 -0500)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
for you to fetch changes up to 9147efcbe0b7cc96b18eb64b1a3f0d4bba81443c:
bpf: add schedule points to map alloc/free (2017-12-12 15:27:22 -0800)
----------------------------------------------------------------
Alexei Starovoitov (1):
Merge branch 'bpf-misc-fixes'
Daniel Borkmann (3):
bpf: fix corruption on concurrent perf_event_output calls
bpf: fix build issues on um due to mising bpf_perf_event.h
bpf: fix broken BPF selftest build
Eric Dumazet (1):
bpf: add schedule points to map alloc/free
arch/um/include/asm/Kbuild | 1 +
kernel/bpf/hashtab.c | 2 ++
kernel/trace/bpf_trace.c | 19 ++++++++++++-------
tools/include/uapi/asm/bpf_perf_event.h | 7 +++++++
tools/testing/selftests/bpf/Makefile | 13 +------------
5 files changed, 23 insertions(+), 19 deletions(-)
create mode 100644 tools/include/uapi/asm/bpf_perf_event.h
next reply other threads:[~2017-12-13 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-13 22:19 Daniel Borkmann [this message]
2017-12-13 22:30 ` pull-request: bpf 2017-12-13 David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171213221912.6036-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox