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 2018-02-28
Date: Wed, 28 Feb 2018 21:27:58 +0100 [thread overview]
Message-ID: <20180228202758.11001-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Add schedule points and reduce the number of loop iterations
the test_bpf kernel module is performing in order to not hog
the CPU for too long, from Eric.
2) Fix an out of bounds access in tail calls in the ppc64 BPF
JIT compiler, from Daniel.
3) Fix a crash on arm64 on unaligned BPF xadd operations that
could be triggered via interpreter and JIT, from Daniel.
Please not that once you merge net into net-next at some point, there
is a minor merge conflict in test_verifier.c since test cases had
been added at the end in both trees. Resolution is trivial: keep all
the test cases from both trees.
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 a5f7add332b4ea6d4b9480971b3b0f5e66466ae9:
net_sched: gen_estimator: fix broken estimators based on percpu stats (2018-02-23 12:35:46 -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 9960d7669eaa42e82a2f4393adf549191de2e587:
test_bpf: reduce MAX_TESTRUNS (2018-02-28 17:49:18 +0100)
----------------------------------------------------------------
Daniel Borkmann (2):
bpf: allow xadd only on aligned memory
bpf, ppc64: fix out of bounds access in tail call
Eric Dumazet (2):
test_bpf: add a schedule point
test_bpf: reduce MAX_TESTRUNS
arch/powerpc/net/bpf_jit_comp64.c | 1 +
kernel/bpf/verifier.c | 42 +++++++++++++--------
lib/test_bpf.c | 4 +-
tools/testing/selftests/bpf/test_verifier.c | 58 +++++++++++++++++++++++++++++
4 files changed, 88 insertions(+), 17 deletions(-)
next reply other threads:[~2018-02-28 20:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 20:27 Daniel Borkmann [this message]
2018-03-02 2:42 ` pull-request: bpf 2018-02-28 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=20180228202758.11001-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;
as well as URLs for NNTP newsgroup(s).