From: Daniel Borkmann <daniel@iogearbox•net>
To: davem@davemloft•net
Cc: ast@fb•com, kafai@fb•com, netdev@vger•kernel.org,
Daniel Borkmann <daniel@iogearbox•net>
Subject: [PATCH net v2 0/3] Couple of BPF fixes
Date: Sun, 18 Dec 2016 01:52:56 +0100 [thread overview]
Message-ID: <cover.1482019225.git.daniel@iogearbox.net> (raw)
This set contains three BPF fixes for net, one that addresses the
complaint from Geert wrt static allocations, and the other is a fix
wrt mem accounting that I found recently during testing and there's
still one more fix on the map value marking.
Thanks!
v1 -> v2:
- Patch 1 as is.
- Fixed kbuild bot issue by letting charging helpers stay in the
syscall.c, since there locked_vm is valid and only export the
ones needed by bpf_prog_realloc(). Add empty stubs in case the
bpf syscall is not enabled.
- Added patch 3 that addresses one more issue in map val marking.
Daniel Borkmann (3):
bpf: dynamically allocate digest scratch buffer
bpf: fix overflow in prog accounting
bpf: fix mark_reg_unknown_value for spilled regs on map value marking
include/linux/bpf.h | 13 ++++++++++++-
include/linux/filter.h | 14 +++++++++++---
kernel/bpf/core.c | 43 +++++++++++++++++++++++++++++--------------
kernel/bpf/syscall.c | 38 +++++++++++++++++++++++++++++---------
kernel/bpf/verifier.c | 17 ++++++++++++-----
5 files changed, 93 insertions(+), 32 deletions(-)
--
1.9.3
next reply other threads:[~2016-12-18 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 0:52 Daniel Borkmann [this message]
2016-12-18 0:52 ` [PATCH net v2 1/3] bpf: dynamically allocate digest scratch buffer Daniel Borkmann
2016-12-18 0:52 ` [PATCH net v2 2/3] bpf: fix overflow in prog accounting Daniel Borkmann
2016-12-18 0:52 ` [PATCH net v2 3/3] bpf: fix mark_reg_unknown_value for spilled regs on map value marking Daniel Borkmann
2016-12-18 2:28 ` [PATCH net v2 0/3] Couple of BPF fixes 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=cover.1482019225.git.daniel@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=ast@fb$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=kafai@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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