From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: daniel@iogearbox.net, ast@kernel.org, netdev@vger.kernel.org,
bpf@vger.kernel.org
Subject: pull-request: bpf 2019-08-31
Date: Sat, 31 Aug 2019 01:40:06 +0200 [thread overview]
Message-ID: <20190830234006.31988-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Fix 32-bit zero-extension during constant blinding which
has been causing a regression on ppc64, from Naveen.
2) Fix a latency bug in nfp driver when updating stack index
register, from Jiong.
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 f53a7ad189594a112167efaf17ea8d0242b5ac00:
r8152: Set memory to all 0xFFs on failed reg reads (2019-08-25 19:52:59 -0700)
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 ede7c460b1da5be7b8ef4efe47f1687babf06408:
bpf: handle 32-bit zext during constant blinding (2019-08-26 23:05:01 +0200)
----------------------------------------------------------------
Jiong Wang (1):
nfp: bpf: fix latency bug when updating stack index register
Naveen N. Rao (1):
bpf: handle 32-bit zext during constant blinding
drivers/net/ethernet/netronome/nfp/bpf/jit.c | 17 +++++++++++++----
kernel/bpf/core.c | 8 ++++++--
2 files changed, 19 insertions(+), 6 deletions(-)
next reply other threads:[~2019-08-30 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 23:40 Daniel Borkmann [this message]
2019-08-31 0:39 ` pull-request: bpf 2019-08-31 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=20190830234006.31988-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.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