From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, tgraf@suug.ch,
jakub.kicinski@netronome.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/3] BPF direct packet access improvements
Date: Tue, 20 Sep 2016 00:26:11 +0200 [thread overview]
Message-ID: <cover.1474323281.git.daniel@iogearbox.net> (raw)
This set adds write support to the currently available read support
for {cls,act}_bpf programs. First one is a fix for affected commit
sitting in net-next and prerequisite for the second one, last patch
adds a number of test cases against the verifier. For details, please
see individual patches.
Thanks!
Daniel Borkmann (3):
bpf, verifier: enforce larger zero range for pkt on overloading stack buffs
bpf: direct packet write and access for helpers for clsact progs
bpf: add test cases for direct packet access
include/linux/bpf.h | 4 +-
include/linux/skbuff.h | 14 +-
include/uapi/linux/bpf.h | 21 +++
kernel/bpf/helpers.c | 3 +
kernel/bpf/verifier.c | 56 ++++--
net/core/filter.c | 134 ++++++++++++--
samples/bpf/test_verifier.c | 433 +++++++++++++++++++++++++++++++++++++++++++-
7 files changed, 627 insertions(+), 38 deletions(-)
--
1.9.3
next reply other threads:[~2016-09-19 22:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 22:26 Daniel Borkmann [this message]
2016-09-19 22:26 ` [PATCH net-next 1/3] bpf, verifier: enforce larger zero range for pkt on overloading stack buffs Daniel Borkmann
2016-09-19 22:26 ` [PATCH net-next 2/3] bpf: direct packet write and access for helpers for clsact progs Daniel Borkmann
2016-09-19 22:26 ` [PATCH net-next 3/3] bpf: add test cases for direct packet access Daniel Borkmann
2016-09-21 3:37 ` [PATCH net-next 0/3] BPF direct packet access improvements 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.1474323281.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
/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.