From: Alexei Starovoitov <ast@kernel.org>
To: <davem@davemloft.net>
Cc: <daniel@iogearbox.net>, <netdev@vger.kernel.org>,
<bpf@vger.kernel.org>, <kernel-team@fb.com>
Subject: pull-request: bpf 2019-03-01
Date: Fri, 1 Mar 2019 21:35:38 -0800 [thread overview]
Message-ID: <20190302053538.642410-1-ast@kernel.org> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) fix sanitation rewrite, from Daniel.
2) fix error path on map_new_fd, from Peng.
3) fix icache flush address, from Paul.
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 3da1ed7ac398f34fff1694017a07054d69c5f5c5:
net: avoid use IPCB in cipso_v4_error (2019-02-25 14:32:35 -0800)
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 3612af783cf52c74a031a2f11b82247b2599d3cd:
bpf: fix sanitation rewrite in case of non-pointers (2019-03-01 21:24:08 -0800)
----------------------------------------------------------------
Daniel Borkmann (1):
bpf: fix sanitation rewrite in case of non-pointers
Paul Burton (1):
MIPS: eBPF: Fix icache flush end address
Peng Sun (2):
bpf: decrease usercnt if bpf_map_new_fd() fails in bpf_map_get_fd_by_id()
bpf: drop refcount if bpf_map_new_fd() fails in map_create()
arch/mips/net/ebpf_jit.c | 2 +-
kernel/bpf/syscall.c | 6 +++---
kernel/bpf/verifier.c | 3 ++-
3 files changed, 6 insertions(+), 5 deletions(-)
next reply other threads:[~2019-03-02 5:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 5:35 Alexei Starovoitov [this message]
2019-03-02 5:48 ` pull-request: bpf 2019-03-01 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=20190302053538.642410-1-ast@kernel.org \
--to=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kernel-team@fb.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.