From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>, netdev@vger.kernel.org
Cc: oss-drivers@netronome.com, alexei.starovoitov@gmail.com
Subject: Re: [PATCH net-next 3/4] bpf: move knowledge about post-translation offsets out of verifier
Date: Tue, 17 Oct 2017 11:38:23 +0200 [thread overview]
Message-ID: <59E5CF8F.10108@iogearbox.net> (raw)
In-Reply-To: <20171016234056.1964-4-jakub.kicinski@netronome.com>
On 10/17/2017 01:40 AM, Jakub Kicinski wrote:
> Use the fact that verifier ops are now separate from program
> ops to define a separate set of callbacks for verification of
> already translated programs.
>
> Since we expect the analyzer ops to be defined only for
> a small subset of all program types initialize their array
> by hand (don't use linux/bpf_types.h).
>
> Signed-off-by: Jakub Kicinski <jakub.kicinski@netronome.com>
Acked-by: Daniel Borkmann <daniel@iogearbox.net>
next prev parent reply other threads:[~2017-10-17 9:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-16 23:40 [PATCH net-next 0/4] bpf: move context info out of the verifier Jakub Kicinski
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 [this message]
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=59E5CF8F.10108@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@netronome.com \
--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).