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-03-29
Date: Thu, 29 Mar 2018 16:38:00 +0200 [thread overview]
Message-ID: <20180329143800.20949-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Fix nfp to properly check max insn count while emitting
instructions in the JIT which was wrongly comparing bytes
against number of instructions before, from Jakub.
2) Fix for bpftool to avoid usage of hex numbers in JSON
output since JSON doesn't accept hex numbers with 0x
prefix, also from Jakub.
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 1bfa26ff8c4b7512f4e4efa6df211239223033d4:
ipv6: fix possible deadlock in rt6_age_examine_exception() (2018-03-23 13:40:34 -0400)
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 e8a4796ee2954db9f7e9b52e5fbc66ef876752f6:
nfp: bpf: fix check of program max insn count (2018-03-24 10:41:24 -0700)
----------------------------------------------------------------
Jakub Kicinski (2):
tools: bpftool: don't use hex numbers in JSON output
nfp: bpf: fix check of program max insn count
drivers/net/ethernet/netronome/nfp/bpf/jit.c | 6 +++++-
tools/bpf/bpftool/map.c | 2 +-
2 files changed, 6 insertions(+), 2 deletions(-)
next reply other threads:[~2018-03-29 14:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-29 14:38 Daniel Borkmann [this message]
2018-03-29 20:33 ` pull-request: bpf 2018-03-29 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=20180329143800.20949-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