From: Daniel Borkmann <daniel@iogearbox.net>
To: davem@davemloft.net
Cc: alexei.starovoitov@gmail.com, netdev@vger.kernel.org,
Daniel Borkmann <daniel@iogearbox.net>
Subject: [PATCH net-next 0/2] More flexible BPF cb access
Date: Thu, 12 Jan 2017 02:21:31 +0100 [thread overview]
Message-ID: <cover.1484182858.git.daniel@iogearbox.net> (raw)
This patch improves BPF's cb access by allowing b/h/w/dw
access variants on it. For details, please see individual
patches.
Thanks!
Daniel Borkmann (2):
bpf: pass original insn directly to convert_ctx_access
bpf: allow b/h/w/dw access for bpf's cb in ctx
include/linux/bpf.h | 7 +-
kernel/bpf/verifier.c | 11 +-
kernel/trace/bpf_trace.c | 15 +-
net/core/filter.c | 176 ++++++-----
tools/testing/selftests/bpf/test_verifier.c | 442 +++++++++++++++++++++++++++-
5 files changed, 563 insertions(+), 88 deletions(-)
--
1.9.3
next reply other threads:[~2017-01-12 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 1:21 Daniel Borkmann [this message]
2017-01-12 1:21 ` [PATCH net-next 1/2] bpf: pass original insn directly to convert_ctx_access Daniel Borkmann
2017-01-12 1:21 ` [PATCH net-next 2/2] bpf: allow b/h/w/dw access for bpf's cb in ctx Daniel Borkmann
2017-01-12 8:25 ` Quentin Monnet
2017-01-12 10:53 ` Daniel Borkmann
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.1484182858.git.daniel@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).