From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: netdev@vger.kernel.org
Cc: oss-drivers@netronome.com, alexei.starovoitov@gmail.com,
daniel@iogearbox.net,
Jakub Kicinski <jakub.kicinski@netronome.com>
Subject: [PATCH net-next 0/4] bpf: move context info out of the verifier
Date: Mon, 16 Oct 2017 16:40:52 -0700 [thread overview]
Message-ID: <20171016234056.1964-1-jakub.kicinski@netronome.com> (raw)
Hi!
Daniel pointed out during the review of my previous patchset that
the knowledge about context doesn't really belong directly in the
verifier. This patch set takes a bit of a drastic approach to
move the info out of there. I want to be able to use different
set of verifier_ops for program analysis. To do that, I have
to first move the test_run callback to a separate structure. Then
verifier ops can be declared in the verifier directly and
different sets can be picked for verification vs analysis.
Jakub Kicinski (4):
bpf: split verifier and program ops
bpf: remove the verifier ops from program structure
bpf: move knowledge about post-translation offsets out of verifier
bpf: allow access to skb->len from offloads
include/linux/bpf.h | 17 ++++++---
include/linux/bpf_types.h | 28 +++++++-------
include/linux/bpf_verifier.h | 1 +
kernel/bpf/syscall.c | 6 +--
kernel/bpf/verifier.c | 70 +++++++++++++++--------------------
kernel/trace/bpf_trace.c | 15 ++++++--
net/core/filter.c | 87 +++++++++++++++++++++++++++++++++++++++-----
7 files changed, 149 insertions(+), 75 deletions(-)
--
2.14.1
next reply other threads:[~2017-10-16 23:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:40 Jakub Kicinski [this message]
2017-10-16 23:40 ` [PATCH net-next 1/4] bpf: split verifier and program ops Jakub Kicinski
2017-10-17 9:37 ` Daniel Borkmann
2017-10-17 15:44 ` Alexei Starovoitov
2017-10-16 23:40 ` [PATCH net-next 2/4] bpf: remove the verifier ops from program structure Jakub Kicinski
2017-10-17 9:38 ` Daniel Borkmann
2017-10-17 15:45 ` Alexei Starovoitov
2017-10-16 23:40 ` [PATCH net-next 3/4] bpf: move knowledge about post-translation offsets out of verifier Jakub Kicinski
2017-10-17 9:38 ` Daniel Borkmann
2017-10-17 15:45 ` Alexei Starovoitov
2017-10-16 23:40 ` [PATCH net-next 4/4] bpf: allow access to skb->len from offloads Jakub Kicinski
2017-10-17 9:38 ` Daniel Borkmann
2017-10-17 15:46 ` Alexei Starovoitov
2017-10-17 9:39 ` [PATCH net-next 0/4] bpf: move context info out of the verifier Daniel Borkmann
2017-10-18 13:17 ` 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=20171016234056.1964-1-jakub.kicinski@netronome.com \
--to=jakub.kicinski@netronome.com \
--cc=alexei.starovoitov@gmail.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
/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).