From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: jakub.kicinski@netronome.com, daniel@iogearbox.net,
ast@kernel.org, netdev@vger.kernel.org, bpf@vger.kernel.org
Subject: pull-request: bpf 2020-01-07
Date: Tue, 7 Jan 2020 10:34:38 +0100 [thread overview]
Message-ID: <20200107093438.10089-1-daniel@iogearbox.net> (raw)
Hi David,
The following pull-request contains BPF updates for your *net* tree.
We've added 2 non-merge commits during the last 1 day(s) which contain
a total of 2 files changed, 16 insertions(+), 4 deletions(-).
The main changes are:
1) Fix a use-after-free in cgroup BPF due to auto-detachment, from Roman Gushchin.
2) Fix skb out-of-bounds access in ld_abs/ind instruction, from Daniel Borkmann.
Please consider pulling these changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git
Thanks a lot!
Also thanks to reporters, reviewers and testers of commits in this pull-request:
Anatoly Trosinenko, Josef Bacik, Song Liu
----------------------------------------------------------------
The following changes since commit 4012a6f2fa562b4b2884ea96db263caa4c6057a8:
firmware: tee_bnxt: Fix multiple call to tee_client_close_context (2020-01-06 13:51:37 -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 6d4f151acf9a4f6fab09b615f246c717ddedcf0c:
bpf: Fix passing modified ctx to ld/abs/ind instruction (2020-01-06 14:19:47 -0800)
----------------------------------------------------------------
Daniel Borkmann (1):
bpf: Fix passing modified ctx to ld/abs/ind instruction
Roman Gushchin (1):
bpf: cgroup: prevent out-of-order release of cgroup bpf
kernel/bpf/cgroup.c | 11 +++++++++--
kernel/bpf/verifier.c | 9 +++++++--
2 files changed, 16 insertions(+), 4 deletions(-)
next reply other threads:[~2020-01-07 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 9:34 Daniel Borkmann [this message]
2020-01-07 21:31 ` pull-request: bpf 2020-01-07 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=20200107093438.10089-1-daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox