From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
Cc: netfilter-devel@vger.kernel.org, Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH] extensions: libxt_bpf: support ebpf pinned objects
Date: Sat, 10 Dec 2016 14:06:58 +0100 [thread overview]
Message-ID: <20161210130658.GA29356@salvia> (raw)
In-Reply-To: <1481234978-40351-1-git-send-email-willemdebruijn.kernel@gmail.com>
On Thu, Dec 08, 2016 at 05:09:38PM -0500, Willem de Bruijn wrote:
> From: Willem de Bruijn <willemb@google.com>
>
> Exercise the new kernel feature introduced in commit 2c16d6033264
> ("netfilter: xt_bpf: support ebpf") to load pinned eBPF programs.
>
> The new interface allows instantiating a bpf match using
>
> -m bpf --object-pinned ${PATH}
>
> where ${PATH} points to a node in a bpf virtual filesystem. See
> also the revised man page.
Applied, thanks Willem.
prev parent reply other threads:[~2016-12-10 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 22:09 [PATCH] extensions: libxt_bpf: support ebpf pinned objects Willem de Bruijn
2016-12-10 13:06 ` Pablo Neira Ayuso [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=20161210130658.GA29356@salvia \
--to=pablo@netfilter.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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).