From: Alexei Starovoitov <ast@plumgrid.com>
To: Daniel Borkmann <daniel@iogearbox.net>, stephen@networkplumber.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH iproute2 -next] examples: bpf: fix ld offs to have same prog loaded on ingress/egress
Date: Mon, 20 Apr 2015 14:17:33 -0700 [thread overview]
Message-ID: <55356CED.2050200@plumgrid.com> (raw)
In-Reply-To: <02fed6731d00ae1af3936c58e363a4e2d1df13e5.1429528359.git.daniel@iogearbox.net>
On 4/20/15 4:48 AM, Daniel Borkmann wrote:
> Fix up the eBPF example program to match our kernel fix in a166151cbe33 ("bpf:
> fix bpf helpers to use skb->mac_header relative offsets"). Tested on ingress
> and egress paths.
>
> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
> Cc: Alexei Starovoitov <ast@plumgrid.com>
> ---
> ( Stephen, this applies on top of "tc: built-in eBPF exec proxy":
> https://patchwork.ozlabs.org/patch/461837/ )
Looks good.
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
prev parent reply other threads:[~2015-04-20 21:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 11:48 [PATCH iproute2 -next] examples: bpf: fix ld offs to have same prog loaded on ingress/egress Daniel Borkmann
2015-04-20 21:17 ` Alexei Starovoitov [this message]
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=55356CED.2050200@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).