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-10-05
Date: Fri, 5 Oct 2018 19:47:13 +0200 [thread overview]
Message-ID: <20181005174713.4737-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
The main changes are:
1) Fix to truncate input on ALU operations in 32 bit mode, from Jann.
2) Fixes for cgroup local storage to reject reserved flags on element
update and rejection of map allocation with zero-sized value, from Roman.
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 d4ce58082f206bf6e7d697380c7bc5480a8b0264:
net-tcp: /proc/sys/net/ipv4/tcp_probe_interval is a u32 not int (2018-09-26 20:33:21 -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 b799207e1e1816b09e7a5920fbb2d5fcf6edd681:
bpf: 32-bit RSH verification must truncate input before the ALU op (2018-10-05 18:41:45 +0200)
----------------------------------------------------------------
Jann Horn (1):
bpf: 32-bit RSH verification must truncate input before the ALU op
Roman Gushchin (2):
bpf: harden flags check in cgroup_storage_update_elem()
bpf: don't accept cgroup local storage with zero value size
kernel/bpf/local_storage.c | 5 ++++-
kernel/bpf/verifier.c | 10 +++++++++-
2 files changed, 13 insertions(+), 2 deletions(-)
next reply other threads:[~2018-10-06 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 17:47 Daniel Borkmann [this message]
2018-10-05 17:56 ` pull-request: bpf 2018-10-05 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=20181005174713.4737-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 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.